Skip to main content
Glama

Coverage

get_coverage
Read-only
The countries, languages and topics World Feed Monitor covers, with the codes to filter by: a country's iso_2 or iso_3, a language's code, a topic's key. Pass `include` to ask for only some of them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoWhich lists to return. Default: all three.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include / items / enum
      Previous value: -[
      -  "countries",
      -  "languages",
      -  "macro_categories"
      -]New value: +[
      +  "countries",
      +  "languages",
      +  "topics"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint annotation already establishes this is a safe read, so the bar is lower, and the description adds real context: it explains that the payload is a vocabulary of filter codes and that subsets can be requested. It omits any note on response shape or caching/stability of the code lists, but for a static reference endpoint that gap is small.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the resource and its codes, with the parameter hint trailing. Slightly loose punctuation (the colon-plus-list construction) costs a point but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema and an existing readOnly annotation, the definition covers what it returns and how to narrow it — enough to invoke correctly. Only the guidance on when to reach for it over siblings is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single `include` parameter already has an enum plus a documented default ('Default: all three'). The description only restates that `include` narrows the result set, adding no format or behavioral meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource returned — countries, languages and topics with their filter codes (iso_2/iso_3, language code, topic key) — which is concrete enough to distinguish it from news-fetching siblings like get_latest_news or search_news. It lacks an explicit verb ('Returns...'/'Lists...'), leaving the retrieval action implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this versus get_publishers or the search tools; the practical use case (resolving valid filter values before querying) must be inferred from 'with the codes to filter by'. The only direct usage instruction covers the `include` parameter, not tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources