Skip to main content
Glama

Recall365 — Global Product Recalls

Data coverage

data_coverage
Read-only

Which official sources are covered, record counts, and the latest publish date per source (how fresh the data is).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-domain read. The description adds the useful disclosure that results include record counts and latest publish dates, i.e. what the payload contains, but says nothing about ordering, granularity, or how sources are identified.

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

Conciseness5/5

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

A single sentence with zero filler; the three returned elements are listed in a natural reading order and the freshness gloss is attached directly to the field it explains.

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 parameterless metadata tool with no output schema, the description adequately covers what comes back (sources, counts, publish dates). It stops short of defining what an 'official source' is or how the result is shaped, but the complexity is low enough that little more is required.

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 nothing for the description to disambiguate and no schema semantics are needed. Baseline for a parameterless tool 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 resource and enumerates its contents: covered official sources, record counts, and latest publish date per source. It is clearly an informational/metadata lookup, distinguishable from siblings like search_recalls or brand_recall_history, though it uses a noun-phrase fragment ('Which official sources are covered...') rather than an explicit verb.

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?

Usage is only implied: an agent can infer this tool answers 'what data exists and how fresh is it' before running a search, and the parenthetical '(how fresh the data is)' hints at freshness checking. There is no explicit when-to-use statement, no prerequisites, and no mention of alternatives among the sibling tools.

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