Skip to main content
Glama

RailCore Developers

Search the RailCore API docs

search_docs
Read-onlyIdempotent

Search the RailCore Indian Railways API documentation: guides (authentication, request signing, rate limits, billing in requests), endpoint pages and error codes. Returns the best matching sections with links. Use it for any how-to question about the API.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoLimit results to guides, endpoints or errors. Default: any.
limitNoHow many results, 1 to 10. Default: 5.
queryYesWhat to look for, in plain words or an error code.

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes
catalog_generated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the useful fact that results are ranked matching sections with links, but says nothing about result quality, whether full pages are returned, or how the limit interacts with ranking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the resource scope front-loaded before the usage instruction. Nothing is restated from the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and the content-domain scoping is adequate for a search tool. The one omission is sibling differentiation, which matters here given the presence of explain_error and get_endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with per-parameter descriptions and an enum for kind, so the schema carries the semantics. The description's mention of 'error codes' loosely mirrors the query parameter but adds no syntax, format, or scoping detail beyond the schema — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and a precisely scoped resource (RailCore Indian Railways API documentation), then enumerates the corpus — guides, endpoint pages, error codes — and the return shape (best matching sections with links). An agent can distinguish this from a single-endpoint or error-lookup tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it for any how-to question about the API" gives a positive trigger, but there are no exclusions and no routing to siblings such as explain_error or get_endpoint. The phrase "any how-to question" is broad enough to overlap with those tools, leaving selection to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources