Skip to main content
Glama

coverage_report

Read-onlyIdempotent

Identify crawl coverage gaps by entity type and optionally list per-concept rows in a read-only inventory, so you can see which data concepts are missing.

Instructions

Crawl-coverage gap inventory (read-only).

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": "coverage_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoInclude per-concept rows (default: summary only).
entity_typeNoFilter to one entity type (fund/stock/country/...).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so "read-only" in the description is repetition rather than added disclosure. Nothing is said about what a "gap" means, how it is computed, or how results are shaped beyond what the output schema provides.

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?

A single front-loaded fragment with zero filler or hedging; nothing needs to be trimmed. The tradeoff is that terseness tips into under-specification rather than crispness.

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

Completeness2/5

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

For a diagnostic/reporting tool with an output schema, the description should at least explain what constitutes a coverage gap and how the result relates to crawl_status or plan_crawl. As written it gives an agent no basis for interpreting the inventory or knowing when it is the right call.

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 coverage is 100%, so both parameters (detail, entity_type) are already documented in the schema, and the description adds nothing about them. Baseline 3 applies because the schema carries the full parameter burden.

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

Purpose3/5

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

"Crawl-coverage gap inventory" is a compact noun phrase that identifies the resource (a coverage-gap listing) but supplies no verb or scope, and it never distinguishes itself from siblings like crawl_status or data_stats. An agent can guess the general subject but not precisely what is returned.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative. The parenthetical "read-only" hints at the operation's nature but gives no condition under which an agent should pick this over crawl_status or plan_crawl.

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