Skip to main content
Glama

get_recall_coverage

Read-only

Read freshness and bounded CPSC corpus scope before querying. Product safety is never certified.

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_recall_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: results reflect data freshness and a bounded CPSC corpus, and 'Product safety is never certified' warns the agent not to treat output as a safety determination. It still doesn't say what the response actually reports (a date, a scope statement, flags), so it is not fully transparent.

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?

Two short sentences with the pre-query timing front-loaded and the safety caveat last, which is a sensible ordering. The compression is aggressive enough that the first sentence reads ambiguously, costing a little clarity.

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

Completeness3/5

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

For a zero-parameter, read-only tool there is little that could go wrong, but with no output schema the description is the only source of information about the return value, and it never says what 'freshness' or 'scope' look like. An agent knows when to call it but not what it will receive.

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

Parameters4/5

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

The tool takes zero parameters, so there is no argument meaning to convey and the schema is complete by construction. Baseline 4 applies.

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?

The description conveys that this returns dataset metadata (freshness and the bounded CPSC corpus scope) rather than recall records themselves, which distinguishes it in spirit from find_recall_candidates. However, the phrasing 'Read freshness and bounded CPSC corpus scope' is compressed and jargon-heavy; it never plainly states the resource being returned, so an agent must infer that this is a corpus-metadata/coverage endpoint.

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

Usage Guidelines4/5

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

'before querying' gives an explicit sequencing cue: call this prior to running recall queries such as find_recall_candidates. There is no statement of when not to call it or what to do if the coverage is stale, so it stops short of full routing guidance, but the intended context is clear.

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