Fetch the newest public Politico stories for a specific section by providing its section slug, returning clean JSON for analysis.
Get Politico section archive. Returns the newest public Politico stories on one section archive page. topic is a section slug -- see politico-categories for the full known value space.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Politico 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. It discloses that results are 'newest public' stories and limited to 'one section archive page', which is useful. However, it does not explain the returned structure, pagination, or any limitations beyond a single page, leaving some ambiguity for an agent.
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?
Two sentences with no wasted words. The core purpose is front-loaded, and the topic guidance is placed where it is most useful. The description is appropriately sized for the tool's simplicity.
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, no-output-schema tool, the description is largely complete: it names the resource, the nature of the results, and where to find valid parameter values. It could add a bit more about the response shape, but the absence of an output schema makes that less critical here.
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?
Schema coverage is 100% and the description adds value beyond the schema by pointing to politico-categories for the 'full known value space'. This is a meaningful hint that the topic values are finite and discoverable, which helps the agent select a valid slug.
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 clearly states the tool retrieves the newest public Politico stories for a specific section archive page. The use of 'section archive' and the explicit topic parameter distinguishes it from sibling tools like politico_headlines, politico_article, and politico_categories.
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 context: use this tool to get newest stories for a specific Politico section. It instructs the agent to consult politico-categories for valid topic slugs, which effectively routes the user to the correct companion tool for parameter selection. It does not explicitly state when not to use the tool, but the context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.