itc_investigation_detail
Pack: usitc-edis · Endpoint: https://gateway.pipeworx.io/usitc-edis/mcp
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/itc_investigation_detail for the schema, then POST the same URL with its arguments for the data.
Full status record for ONE USITC investigation, by its internal investigation_id (from itc_investigation_search — NOT the human “337-TA-1400” number). KEYLESS. Returns status, phase, category, docket number, every procedural date on file (institution, Federal Register notice, initial determination, target date, hearing schedule, AD/CVD determination dates), and counts of related/consolidated/severed investigations. Does NOT include filed documents (use edis_document_list with the investigation_number) or ITC staff/case-manager identity (deliberately excluded).
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
investigation_id | string | yes | Internal numeric id, e.g. “8977” (from itc_investigation_search). |
Example call
Arguments
{
"investigation_id": "9005"
}
curl
curl -X POST https://gateway.pipeworx.io/usitc-edis/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"itc_investigation_detail","arguments":{"investigation_id":"9005"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('itc_investigation_detail', {
"investigation_id": "9005"
});
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"usitc-edis": {
"url": "https://gateway.pipeworx.io/usitc-edis/mcp"
}
}
}
See Getting Started for client-specific install steps.