Paw Multiverse pet food recalls

List the registers and how fresh each one is

list_recall_registers

Return every official register this record reads, with the authority that publishes it, its licence, how many entries are held from it, how often it is read, and the last time it was read without error. Use this before quoting the record to establish how current it is, and to tell someone which countries are covered and which are not. A country that is not listed here is not covered, and nothing should be inferred about it.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does substantially: it discloses the exact data returned, implies the operation is a pure read, and adds the important semantic caveat that absence from the list means non-coverage rather than missing data. It omits ordering, pagination, or empty-list behavior, which are the remaining gaps.

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?

Three short sentences, front-loaded with what is returned, followed by the usage trigger and the negative-coverage rule. No filler or restatement of the name.

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

Completeness5/5

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

No output schema exists, yet the description effectively serves as one by listing the returned attributes. Combined with the coverage caveat, an agent has everything needed to call this and interpret the result correctly.

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 the baseline is 4; the description correctly implies no input is needed and instead spends its words on output semantics. There is no parameter ambiguity to compensate for.

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

Purpose5/5

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

States a specific verb and resource ('Return every official register this record reads') and immediately enumerates the returned fields — publishing authority, licence, entry count, read frequency, last successful read. That field-level specificity makes it clearly distinguishable from record-fetching or search siblings without needing to name them.

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?

Gives a concrete trigger: use it before quoting the record to establish currency, and to explain country coverage. It also states an exclusion-style rule ('a country that is not listed here is not covered'). It does not explicitly name sibling tools or say when another tool is preferable, which keeps it below a 5.

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

All Paw Multiverse pet food recalls tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?