List the seven NBC News RSS section slugs accepted by nbc-headlines, including each section's slug, display name, and URL.
Get NBC News RSS sections. Lists the seven NBC News section slugs accepted by nbc-headlines: news, world, us-news, politics, business, science and health. Each entry has its slug, display name and 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, so the description carries the load, and it does: it discloses the source (RSS sections), that the result is a fixed list of seven entries, and the shape of each entry (slug, name, url). Little else is needed for a static read-only lookup, though nothing is said about caching or stability of the list.
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 purpose, followed by the concrete slug list and the return shape. No filler and nothing repeated from structured fields.
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 listing tool, the description supplies everything an agent needs: what it returns, the exact values, and which sibling consumes them.
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 no parameters, so the baseline is 4. The enumeration of slugs is technically input for the sibling `nbc-headlines`, but it usefully documents the value space this tool produces.
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 NBC News RSS sections') and enumerates exactly what the tool returns: the seven section slugs, names and URLs. It also names the sibling `nbc-headlines` it exists to serve, so an agent can place it without opening the schema.
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?
Strongly implies the call pattern by stating the slugs are 'accepted by `nbc-headlines`', routing the agent to the dependent tool. It stops short of an explicit 'call this before nbc-headlines' instruction, but the context is unambiguous for a zero-param lookup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.