edge_cases_test_file
Pack: edge-case-museum · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/edge_cases_test_file for the schema, then POST the same URL with its arguments for the data.
Edge Case Museum: one runnable test file (pytest for python, node:test for javascript) bundling the inputs from the exhibits relevant to what you are implementing, as parametrized cases you point at your own function. The file runs as generated against a stub, with TODO marks where your function goes; each case names its exhibit id so edge_case_get can explain a failure.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
context | string | yes | What you are implementing, e.g. “parse a CSV upload”. |
language | string | yes | python produces a pytest file; javascript produces a node:test file. |
Example call
Arguments
{
"context": "parse a CSV upload",
"language": "python"
}
curl
curl -X POST https://gateway.pipeworx.io/edge-case-museum/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"edge_cases_test_file","arguments":{"context":"parse a CSV upload","language":"python"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('edge_cases_test_file', {
"context": "parse a CSV upload",
"language": "python"
});
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the edge-case-museum pack
{
"mcpServers": {
"edge-case-museum": {
"url": "https://gateway.pipeworx.io/edge-case-museum/mcp"
}
}
}
See Getting Started for client-specific install steps.