Paw Multiverse pet food recalls

List products recalled in more than one country

cross_border_recalls

Return the products that appear in more than one country register, matched on barcode: the same item recalled by two or more authorities. This view exists nowhere else, including at the authorities themselves, each of which publishes only its own country. Use it to answer whether a recall in one country has a counterpart elsewhere. A product appearing in only one country here has not been shown to be safe in the others; it has only not been matched.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations supplied, the description carries the burden and does real work: it discloses the matching mechanism (barcode), the fact that authorities publish only their own country so this view is derived, and an important interpretive caveat that a single-country hit 'has not been shown to be safe.' It omits return shape, ordering, and result size, which keeps it from a 5.

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?

Three sentences, front-loaded with the definition, then usage, then the caveat. Every sentence contributes, though 'including at the authorities themselves, each of which publishes only its own country' is slightly wordy for the point it makes.

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 zero-parameter tool with no output schema and no annotations, the description covers what qualifies, why the view exists, and how to interpret non-matches. The main remaining gap is that it never says what a returned entry contains (e.g., which country registers, barcode, names), which an agent might need to report results.

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 usefully explains the matching key that governs which records qualify, which is the only semantics that matter for a no-argument tool.

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?

The description states a specific verb and resource plus the defining filter: products appearing in more than one country register, matched on barcode. It also distinguishes this from sibling listing/search tools by explaining that this cross-register intersection view 'exists nowhere else,' so an agent can tell it apart without opening another schema.

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?

It gives an explicit use case: 'Use it to answer whether a recall in one country has a counterpart elsewhere,' and it warns against misreading absence of a match as safety. It does not name a sibling alternative or state when not to use it, but the guidance is clear enough to route correctly.

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?