Fetch fresh headlines from a chosen Metro section feed by passing its section slug; returns clean JSON for that section.
Get Metro section headlines. Returns fresh headlines from one public Metro section feed. The section must be a slug returned by the sections endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Metro section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden itself. It discloses that this is a read from a public feed, describes the output as fresh headlines, and constrains valid inputs to slugs from the sections endpoint. It doesn't detail output shape or pagination, but those are not critical for this simple read operation.
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?
Three short sentences with no fluff. The operation is front-loaded, and each following sentence adds a useful constraint or clarification.
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 single-parameter headline feed with no output schema, the description covers what is returned, how to choose a valid section, and that the feed is public and fresh. It could mention where to get full article content, but that is not required to invoke this tool correctly.
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 schema already provides full coverage with an enum and description. The description adds practical meaning by explaining that the section slug must come from the sections endpoint, which helps the agent produce a valid value beyond just choosing from the enum.
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?
The description states the exact operation and resource: 'Get Metro section headlines.' The second sentence clarifies scope as one public Metro section feed, and the name/description clearly distinguish headlines from article content or section enumeration.
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 description gives clear usage context: fetch fresh headlines for a Metro section, and it explicitly tells the agent that the section must be a slug returned by the sections endpoint. It doesn't mention sibling alternatives like metro_news or metro_article, so it stops just short of full explicit exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.