Skip to main content
Glama

rta_search_metro_stations

Read-onlyIdempotent

Search Dubai Metro stations on operating lines (Red, Green, Route 2020). Filter by line and limit results. Excludes future Blue and Gold lines.

Instructions

Search Dubai Metro stations via Dubai Pulse.

Tier 1, requires Dubai Pulse credentials.

Covers operating lines only. Blue Line (under construction, opening 2029-09-09) and Gold Line (approved 2026, opening 2032-09-09) stations are not in the dataset yet.

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": "rta_search_metro_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoOptional line filter (Red, Green, Route 2020).
limitNoMax records.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context: the credential/tier requirement and the fact that Blue and Gold Line stations are absent from the dataset, which prevents the agent from wrongly concluding a station doesn't exist.

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?

Three short, front-loaded sentences with no filler: purpose, access requirement, coverage caveat. The construction-date details for Blue/Gold Line are slightly verbose but they directly justify why those lines are missing.

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

Completeness5/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 described. The description covers the source, the access tier, and the dataset boundary — everything an agent needs beyond the structured fields to call this correctly.

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% — the schema already documents 'line' (Red, Green, Route 2020) and 'limit' (max records). The description adds no syntax or format guidance beyond that, so the baseline 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?

States a specific verb+resource ('Search Dubai Metro stations') and names the upstream source (Dubai Pulse), so the agent knows exactly what data is returned. Sibling differentiation is only implicit — it doesn't say it is the metro counterpart to rta_search_bus_routes — 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 Guidelines3/5

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

It gives prerequisites ('Tier 1, requires Dubai Pulse credentials') and a scope constraint ('operating lines only'), which tells the agent when this tool is valid. However, it never names an alternative tool or states when not to use it (e.g. vs rta_search_bus_routes or rta_gtfs_static_url), so routing guidance is only implied.

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

Deploy Server

Other Tools