Skip to main content
Glama

RailCore Developers

Get one RailCore API endpoint

get_endpoint
Read-onlyIdempotent

Details of one RailCore API endpoint: method and URL, parameters, what it costs in requests, the key scope it needs, which plans can use it and whether requests must be signed, response fields and the errors it can answer. Accepts an endpoint id (seat-availability), a method and path (GET /trains/{train_number}/live) or a full URL.

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": {
      "endpoint": "<endpoint>"
    },
    "name": "get_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNosummary (default) or full, which adds response fields and a response example.
endpointYesAn endpoint id (seat-availability), a method and path (GET /availability/seats) or a URL.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
costYes
notesYes
scopeYes
titleYes
errorsYes
methodYes
signingYes
summaryYes
docs_urlYes
parametersYes
body_fieldsNo
descriptionYes
availabilityYes
markdown_urlYes
response_fieldsNo
signing_requiredYes
body_example_jsonNo
catalog_generated_atYes
response_example_jsonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds real context: the returned record discloses request cost, required scope, plan gating and signing requirements, which tells the agent this is a pre-flight check for calling the underlying API. It does not discuss caching, rate limits, or failure behavior for unresolvable endpoint arguments, so it stops short of a 5.

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

Conciseness4/5

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

Two sentences, front-loaded with the resource and scope of the returned data, with no filler preamble. The long enumeration of returned fields is dense but each item is informative, so it earns its space.

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?

An output schema exists, so the description need not explain return values, and the schema fully documents both parameters; the description's job is to establish what lookup key forms work, which it does. The only gap is the unreconciled 'detail' mode, which the description implies is unnecessary even though it defaults to summary.

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% and the description's input guidance ('endpoint id (seat-availability), a method and path (GET /trains/{train_number}/live) or a full URL') closely mirrors the schema's own examples, adding little new meaning. It also omits the 'detail' parameter entirely and describes response fields as always returned, whereas the schema says they only appear with detail=full, leaving a mild mismatch an agent must resolve from the schema.

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?

Names a specific verb+resource ('Details of one RailCore API endpoint') and then enumerates exactly what those details comprise: method and URL, parameters, request cost, required scope, plan eligibility, signing requirement, response fields and errors. This is concrete enough to distinguish it from siblings like get_code_sample or get_plans without inspecting any 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?

The description establishes the input forms an agent can use (endpoint id, method+path, or full URL), which implies the lookup scenario, but it never states when to prefer this over search_docs or explain_error, nor any exclusions. Usage is inferable from the name and the enumerated detail set rather than stated explicitly.

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