Skip to main content
Glama

RailCore Developers

Compare RailCore API plans

get_plans
Read-onlyIdempotent

RailCore API plans: monthly price in INR, requests a month, per minute and per day, which plans must sign requests, IP allowlists, and which include charts and jobs. Pass a plan name to see one plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoA plan name or id, such as Growth. Leave out to compare all plans.

Output Schema

NameRequiredDescriptionDefault
plansYes
pricing_urlYes
signing_ruleYes
catalog_generated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the behavioral nuance that omitting the parameter returns the full plan set for comparison, which is useful. It says nothing further about response shape or ordering, but with an output schema present that is not required.

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, the first front-loading the resource and its returned fields, the second covering the single parameter's effect. The field enumeration is dense but each item is informative rather than filler. Minor cost: the field list is a comma run with no structural grouping.

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?

This is a simple single-parameter, read-only lookup plus an output schema, and the description covers what data comes back and how filtering works. Safety and idempotency are handled by annotations. Nothing essential for correct invocation is missing, though a note on how plan names are matched would round it out.

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 parameter description already states 'A plan name or id, such as Growth. Leave out to compare all plans.' The description's 'Pass a plan name to see one plan' restates that same guidance without adding format, casing, or matching-behavior detail. With the schema doing the heavy lifting, the baseline of 3 applies.

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

Purpose4/5

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

The description names the resource (RailCore API plans) and enumerates the specific fields returned: monthly price in INR, requests per month/minute/day, request-signing requirements, IP allowlists, charts and jobs. This is concrete enough for an agent to know exactly what data it gets. It lacks an explicit leading verb (list/compare) and doesn't reference siblings, but none of the siblings (get_code_sample, get_endpoint, explain_error, search_docs) overlap with plan comparison, so differentiation is not an issue.

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

Usage Guidelines4/5

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

The final sentence plus the schema jointly explain the two usage modes: supply a plan name to retrieve one plan, or omit it to compare all plans. That is clear context for calling the tool. There are no exclusions or alternative-tool routing, but no competing tool exists for this data, so the omission is minor.

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