Skip to main content
Glama

Vet Adverse Events

vet_adverse_events
Read-onlyIdempotent

Search FDA (openFDA Center for Veterinary Medicine) reports of side effects/adverse events in animals given a veterinary drug or parasite preventive, dogs, cats, horses, cattle. Answers "what side effects has Bravecto caused in dogs", "adverse events for fluralaner in cats", "has anyone reported seizures after ivermectin in dogs". Pass a brand/product name via "drug" OR a chemical active ingredient via "active_ingredient" (either works, the tool resolves brand names against the ingredient field, since that is where product names are actually recorded upstream). Reports are spontaneous submissions, not a validated causal or incidence study.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drug": "Bravecto",
      "species": "Dog"
    },
    "name": "vet_adverse_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugNoBrand/product name, e.g. "Bravecto", "Frontline", "Heartgard".
breedNoOptional: filter to a breed, e.g. "German Shepherd", "Labrador".
limitNoMax reports to return (1-50, default 10).
sinceNoOptional: only reports received on/after this date, YYYY-MM-DD.
speciesYesAnimal species: Dog, Cat, Horse, Cattle, Swine, etc. Case-insensitive.
reactionNoOptional: filter to a specific reaction/symptom, e.g. "vomiting", "seizure", "lethargy".
active_ingredientNoChemical active ingredient, e.g. "fluralaner", "ivermectin", "moxidectin". Use this OR "drug".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: reports are spontaneous submissions and not a validated causal or incidence study, and brand names are resolved against the upstream ingredient field. It does not describe return shape or how limit interacts with total matches, keeping it at 4.

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?

Front-loaded with verb, source and the three canonical questions, then the parameter rule, then the caveat — a logical order with no filler. The three quoted example queries are somewhat redundant with the schema examples, which is the only thing keeping it below 5.

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 7-parameter, no-output-schema tool, the definition covers scope, required species, parameter interchangeability and the spontaneity caveat well. It leaves the return content (report fields, whether counts are included) unspecified, which the absence of an output schema makes slightly more consequential.

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 3 would be the floor, but the description genuinely adds semantics: drug and active_ingredient are interchangeable because brand names are resolved against the ingredient field upstream — a non-obvious behavior the schema alone does not convey. Example value pairings (Bravecto/Dog, fluralaner/vomiting) further clarify intent.

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: search FDA openFDA Center for Veterinary Medicine adverse-event reports, scoped to animals given a veterinary drug or parasite preventive. The three quoted example questions pin down the exact query shape, and the sibling vet_adverse_event_summary is clearly a different (summary) operation. An agent can distinguish this from every listed sibling without opening a 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?

Gives clear trigger contexts via natural-language example questions and explains the drug-vs-active_ingredient choice, plus the required species scope. It stops short of any explicit exclusion (e.g., 'for aggregate counts use vet_adverse_event_summary') and does not state when not to use it, so a 4 rather than a 5.

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.