Retrieve current AP News fact-check headlines from its public page to verify claims and track misinformation. Returns clean JSON for research and monitoring.
Get AP News fact checks. Returns current headlines from AP News' public Fact Check page. The service does not bypass authentication or access controls. Billing is 1 credit, or 5 credits when browser rendering is required.
| 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 behavioral burden and does add real value: it discloses the billing model (1 credit, or 5 when browser rendering is required) and a compliance note that it does not bypass auth or access controls. It stops short of describing latency, caching, or result volume, but the cost/rendering disclosure is substantive.
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 purpose before the billing and compliance notes. No redundancy or filler, though the middle sentence slightly restates the first.
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 tool with no output schema, the description states what comes back (current headlines) and adds billing and compliance context. It is complete enough to call correctly; only minor return-format detail (pagination, item count) is absent.
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 (schema coverage 100%, empty properties), so there are no parameter semantics to convey. Baseline of 4 applies per the 0-param rule.
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 AP News fact checks") and clarifies the source is the Fact Check page, which distinguishes it in spirit from the general apnews_headlines/apnews_news siblings. However, it never names those siblings explicitly, so differentiation relies on the agent inferring that this is the fact-check-specific feed.
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?
Usage is implied by "fact checks" and "Fact Check page," but there is no explicit when-to-use or when-to-prefer-an-alternative guidance, and no mention of apnews_headlines or apnews_news as options. Adequate but leaves routing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.