Retrieves all Metro section slugs with display names and public RSS feed URLs for use with the headlines endpoint.
Get Metro sections. Returns every Metro section slug accepted by the headlines endpoint, with its display name and public RSS feed URL.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns a comprehensive list ('every Metro section slug') and specifies the response contents (display name and public RSS feed URL). For a simple read-only lookup, this is adequate behavioral/return transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads the action and then adds the essential details. No filler or repetition; every word contributes value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, no-output-schema tool, the description is complete: it says what it retrieves, the scope of that retrieval, and exactly which fields are returned. Nothing an agent needs to call or interpret the result is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema description coverage is 100%, so the baseline is 4. The description adds no parameter-specific semantics, but none are needed since the input schema is already empty and fully clear.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states a specific verb and resource ('Get Metro sections') and clarifies the exact scope: every Metro section slug accepted by the headlines endpoint. This differentiates it from the many sibling *_sections tools and ties it directly to the metro_headlines workflow.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'accepted by the headlines endpoint' clearly implies when to use this tool: as a lookup for valid section slugs before calling metro_headlines. It does not explicitly name alternatives or state when not to use it, but the context is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.