Fetch the complete inventory of ProPublica topics to validate section names before querying headlines.
Get ProPublica topics. Returns the complete public topic inventory accepted by /api/v1/propublica/headlines.
| 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?
With no annotations, the description carries the full burden. It discloses that the tool returns a complete inventory and connects it to the headlines endpoint, but it does not mention read-only status, pagination, sorting, or return format. For a zero-parameter getter this is acceptable but not richly transparent.
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 concise sentences, with the primary purpose front-loaded. The second sentence adds a specific, useful detail about the endpoint the inventory serves. No wasted words.
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 simple zero-parameter, no-output-schema tool, the description covers the essential purpose and relationship to the headlines endpoint. Minor gap: it doesn't specify the parameter name that the topics correspond to, but overall it is sufficient for an agent to call it 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?
There are zero parameters and the schema is empty (100% coverage). The baseline for 0 parameters is 4. The description adds nothing about parameters because none exist, which is appropriate.
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 action (Get) and resource (ProPublica topics), and specifies that it returns the complete public topic inventory accepted by /api/v1/propublica/headlines. This distinguishes it from sibling tools like propublica_headlines (which fetches headlines) and propublica_article (which fetches articles).
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 implies usage: it provides the topic inventory for the headlines endpoint, so it should be used when a valid list of topics is needed. It does not explicitly contrast with alternatives or state when not to use it, but the context is clear enough for an agent to select it over siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.