Paw Multiverse pet food recalls

Ask a question about pet food recalls

ask_recall_record

Ask in plain language about a brand, product, barcode, lot code, country or reason ("Has Purina been recalled in the UK?", "salmonella recalls in France in 2025"). Returns a short answer written only from the matching official notices, with numbered sources (URL, date, country, brand, product, reason, lot codes, barcodes, official notice). Coverage is the US, UK, Canada and France. A question with no match is not evidence that a product is safe; say so.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "ask_recall_record"
  }
}

Input Schema

Name	Required	Description	Default
`question`	Yes	The question, in any wording. Up to 300 characters.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it states the answer is grounded only in matching official notices, enumerates the source fields returned, names the covered countries, and warns that absence of a match is not evidence of safety. It does not discuss latency, result-count limits, or how conflicting notices are handled.

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?

The definition is front-loaded with the capability and the example phrasings are compact and illustrative rather than filler. The final two sentences are dense but each carries distinct information — coverage scope and the safety-inference caveat — so little could be cut without losing value.

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?

With no output schema, the description still tells the agent what a response looks like (short grounded answer plus numbered sources with URL, date, country, brand, product, reason, lot codes, barcodes, official notice). Combined with the stated coverage and the no-match caveat, an agent has everything needed to call this correctly and interpret the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by enumerating the facets a question may target — brand, product, barcode, lot code, country, reason — which the schema does not list. The only thing left purely to the schema is the 300-character limit and 'any wording' phrasing.

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 opens with a specific verb and resource ('Ask in plain language about a brand, product, barcode, lot code, country or reason') and immediately distinguishes itself from structured lookup siblings by being natural-language Q&A over official notices. An agent can tell this is a question-answering layer rather than a record fetcher or list tool.

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?

Two inline example questions show the intended input shape and the stated geographic coverage (US, UK, Canada, France) implicitly excludes questions about other countries. It also adds a decision-relevant caveat about interpreting no-match results. What's missing is an explicit pointer to the sibling to use for structured filtering or single-record lookup.

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?