Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

ie_rail

Live Irish Rail departures and arrivals for a named station.

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": {
      "station": "<station>"
    },
    "name": "ie_rail"
  }
}

Input Schema

NameRequiredDescriptionDefault
minsNoLook-ahead window in minutes (default 30, max 90)
stationYesStation name, e.g. Dublin Connolly, Dublin Heuston, Cork, Galway

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / properties / mins
      Added value: +{
+  "description": "Look-ahead window in minutes (default 30, max 90)",
+  "type": "integer"
+}
    • addedInput schema / properties / station
      Added value: +{
+  "description": "Station name, e.g. Dublin Connolly, Dublin Heuston, Cork, Galway",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "station"
+]
  4. Added

TDQS

B3.1/5.0
Behavior2/5

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

No annotations, so the description carries full behavioral burden. 'Live' signals real-time data, which is useful, but nothing is said about rate limits, data freshness, error behavior for bad station names, or the shape of the response. For a zero-annotation tool this is a significant gap.

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?

One sentence, front-loaded with the core resource, zero filler. Appropriately sized for a simple two-parameter read tool.

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

Completeness3/5

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

A simple read tool with full schema coverage and no output schema, so the description needn't explain return values. However, with no annotations the description could still say more about the live-data nature and error handling. Adequate but with clear gaps.

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 description coverage is 100%, with both the station examples and the mins default/max range documented in the schema. The description adds only 'named station', which restates the schema. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

States a specific verb+resource: live Irish Rail departures and arrivals for a named station. Clearly distinct from siblings like ie_weather or ie_stats. It stops short of differentiating behavior between departures and arrivals retrieval, but the resource is unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives, no prerequisites, no mention of what happens with an unrecognized station name. The usage is only implied by the phrase 'for a named station'.

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

All GadgetHumans API Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources