Get all usable Express Tribune RSS sections from the publisher's directory, excluding talko because its official endpoint returns an empty response.
Get The Express Tribune sections. Returns every usable feed section listed in the publisher's RSS directory. talko is omitted because its official endpoint currently returns an empty response.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses a data-completeness caveat (talko omitted because its endpoint returns empty), which is genuine behavioral context beyond the schema. However, it says nothing explicit about read-only status, auth, or the format the sections are returned in.
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, front-loaded with the core purpose, then the scope and the omission caveat. Every sentence earns its place, though the talko detail is arguably optional.
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 listing tool with no output schema, the description adequately covers what the tool returns and its scope. The one gap is not specifying the identifier format of the returned sections (slug vs. display name), which an agent would need to chain into article/headline calls.
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 takes zero parameters, so the baseline of 4 applies. There is nothing for the description to disambiguate beyond what the empty schema already conveys.
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?
States a specific verb and resource ('Get The Express Tribune sections') and clarifies it returns feed sections from the publisher's RSS directory, which distinguishes it from the article/headlines/news siblings. It doesn't explicitly name a sibling alternative, but the resource is concrete and unambiguous.
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?
No guidance on when to call this versus expresstribune_headlines, expresstribune_news, or expresstribune_article. The 'RSS directory' framing implies it is a discovery/navigation tool, but that inference is left entirely to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.