On this page
Reference
ctx_routes
Input contract and parameters for ctx_routes.
MCP tool · Search & code intelligence
Call this tool through your MCP client. Its availability depends on your active configuration and profile.
This registry contract is separate from the SDK. For terminal commands, use the CLI reference.
Parameters
Generated from the registered input schema. “Required” reflects the schema; individual actions can impose additional requirements.
methodstringGET|POST|PUT|DELETE
pathstringPath prefix, e.g. /api/users
Exact JSON schema
Inspect the complete input schema
{
"properties": {
"method": {
"description": "GET|POST|PUT|DELETE",
"type": "string"
},
"path": {
"description": "Path prefix, e.g. /api/users",
"type": "string"
}
},
"required": [],
"type": "object"
}Runtime description
The following is the tool's own agent-facing description, reproduced from the reviewed registry. It can contain implementation terminology; it does not expand the public stability commitment.
Read the agent-facing description
Discover HTTP API endpoints without reading route definition files.
Auto-detects: Express, Flask, FastAPI, Actix, Spring, Rails, Next.js.
method=GET|POST filters by verb; path='/api' filters by prefix.
ANTIPATTERN: not for filesystem paths — use ctx_tree.
Saves tokens vs grepping route definitions.Sources & versions
- mcp_manifest.rsrust/src/core/mcp_manifest.rsReviewed checkout
- registry.rsrust/src/server/registry.rsReviewed checkout
- dynamic_tools.rsrust/src/server/dynamic_tools.rsReviewed checkout
- Core checkout
50fbff09c9- Installed runtime
- 3.10.2
- SDK release
- 1.1.0
Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.
Versions & compatibility