Stories covered by only one side of the political spectrum — reported by left-leaning outlets but not right-leaning, or vice versa. Each source carries a bias score from -2 (left) to +2 (right); 0 is center or non-political. Useful for finding what a given audience is not being told.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max stories, up to 200. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It explains the concept of blindspots and the bias score, but does not disclose response format, pagination, or whether limit defaults are applied. The read-only nature is implied but not stated. It adds moderate value beyond the tool name.
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?
The description is two sentences, each earning its place: the first defines the tool's output, and the second explains the bias scoring and use case. It is concise, front-loaded, and free of fluff.
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?
Given only one parameter, no output schema, and no annotations, the description offers sufficient context for an agent to understand what the tool does and when to use it. It explains the underlying concept and scoring, but lacks explicit details about the return structure or limit behavior.
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% for the only parameter (limit), which is described as 'Max stories, up to 200.' The description does not mention limit, so it adds no extra meaning beyond the schema. Baseline 3 applies.
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 returns stories covered by only one side of the political spectrum, distinguishing it from the sibling tool get_news. It also explains the bias score scale, adding specificity to the resource.
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 provides a clear use case: 'finding what a given audience is not being told.' It implies this tool is for blindspots rather than general news, but does not explicitly name when not to use it or compare with get_news.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct facet: news retrieval, cross-outlet wording comparison, one-sided story detection, and feed health diagnostics. Potential overlap between get_news with view=stories and compare_coverage is mitigated by clearly splitting headline grouping from side-by-side wording analysis.
All four tool names follow a consistent snake_case verb_noun pattern. Three use the get_ prefix (get_news, get_blindspots, get_feed_health) and compare_coverage uses the same verb-first style with a clear object.
Four tools is a well-scoped size for a news bias analysis server. Every tool has a distinct responsibility and the set feels intentionally curated rather than sparse or bloated.
The tool surface covers the full workflow of the domain: retrieving the news, comparing differing coverage of the same event, finding coverage blindspots, and verifying data freshness. There are no obvious pipeline dead ends or major missing operations.
