list_federal_rules
Pack: federal-rules · 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/list_federal_rules for the schema, then POST the same URL with its arguments for the data.
List every rule in a federal court rules set with its number and title: FRCP (civil procedure), FRE (evidence), FRAP (appellate), FRCrP (criminal procedure) or FRBP (bankruptcy). Also returns the “as amended to” date the publisher states for the set. Use to find the rule number before get_federal_rule.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
set | string | yes |
Example call
Arguments
{
"set": "fre"
}
curl
curl -X POST https://gateway.pipeworx.io/federal-rules/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_federal_rules","arguments":{"set":"fre"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('list_federal_rules', {
"set": "fre"
});
Response shape
| Field | Type | Description |
|---|---|---|
set | string | |
set_name | string | |
count | number | |
as_amended_to | string | |
rules | array | |
source | string |
Full JSON Schema
{
"type": "object",
"properties": {
"set": {
"type": "string"
},
"set_name": {
"type": "string"
},
"count": {
"type": "number"
},
"as_amended_to": {
"type": "string"
},
"rules": {
"type": "array",
"items": {
"type": "object",
"properties": {
"rule": {
"type": "string"
},
"title": {
"type": "string"
}
},
"additionalProperties": true
}
},
"source": {
"type": "string"
}
},
"additionalProperties": true
}
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 federal-rules pack
{
"mcpServers": {
"federal-rules": {
"url": "https://gateway.pipeworx.io/federal-rules/mcp"
}
}
}
See Getting Started for client-specific install steps.