Skip to main content
Glama

Toxic food check for dogs and cats

check_toxic_food
Read-onlyIdempotent

Check whether something a dog or cat ate is toxic (chocolate, xylitol, onion/garlic, macadamia, grapes/raisins, lilies, caffeine, alcohol), and — given the pet's weight and the amount eaten — the emergency level, using dose thresholds from the Merck Veterinary Manual. A substance not in the list is NOT confirmed safe. Triage aid, not a diagnosis.

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": {
      "substance": "<substance>"
    },
    "name": "check_toxic_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: ko (Korean) or en (English)ko
variantNoVariant key or label if known (e.g. 'milk', 'dark', 'baking'); the response lists the variants
substanceYesWhat the pet ate, in Korean or English, e.g. 'dark chocolate', '포도', 'xylitol gum'
amount_countNoAmount eaten as a count of pieces (used when grams are unknown)
amount_gramsNoAmount eaten in grams
pet_weight_kgNoPet's body weight in kg

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: the thresholds come from the Merck Veterinary Manual, the result is an emergency level scaled to weight and dose, and the substance list is closed rather than exhaustive — all decision-relevant for an agent interpreting a negative result.

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 core verb and resource, and every clause carries information (substance coverage, computation basis, caveats). The parenthetical substance list is long but earns its place by letting an agent match inputs without guessing coverage.

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 six-parameter tool with no output schema, the description does the necessary work: it explains what is returned (a toxicity verdict plus an emergency level, and that variants are listed) and where thresholds originate. Only minor gaps remain, such as how the two amount inputs interact when both are supplied.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (lang, variant, substance, amount_count, amount_grams, pet_weight_kg) is already documented in the schema. The description only links weight and amount to the dose-threshold calculation, which is a modest addition beyond the structured fields; baseline 3 applies.

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 ('Check whether something a dog or cat ate is toxic') and enumerates the covered substances (chocolate, xylitol, grapes/raisins, lilies, etc.). It also names the computed output ('emergency level') from weight and amount, which no sibling tool (find_vets, get_breed, find_pet_travel, find_rescue_animals) does.

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 sets clear scope boundaries: 'A substance not in the list is NOT confirmed safe' and 'Triage aid, not a diagnosis,' which tells the agent both when the answer is usable and when it must not be treated as authoritative. It does not name an alternative tool, but no sibling covers this domain, so there is little to route against.

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