Skip to main content
Glama
lzinga

US Government Open Data MCP

by lzinga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

fda_animal_events

Read-onlyIdempotent

Search 1.3M+ animal adverse event reports to find drug side effects in dogs, cats, horses, and other species by species, drug, reaction, or date range.

Instructions

Search animal/veterinary adverse event reports (1.3M+ reports). Reports of drug side effects in animals — dogs, cats, horses, cattle, etc. Each report has: animal info (species, breed), drugs, reactions (VEDDRA terms), outcomes. Note: Some fields may contain 'MSK' (masked) values for privacy.

Example searches:

  • 'animal.species:"Dog"' — dog events

  • 'original_receive_date:[20200101+TO+20231231]' — events in date range

  • 'serious_ae:true' — serious adverse events only

Count fields: animal.species.exact, primary_reporter.exact, serious_ae

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10, max 100)
searchNoOpenFDA search query. Examples: 'field:value', 'field:"Exact Phrase"', 'field:[20200101+TO+20231231]', '_exists_:field'. Combine with '+AND+', '+OR+', '+NOT+'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.9.14
    • addedInput schema / properties / limit / default
      Added value: +10
  2. Changed1 schema field changedv2026.4.11
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv2026.3.9

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds useful data-level context: 1.3M+ report scale, field composition, the 'MSK' privacy masking warning, and count fields. No contradiction with annotations.

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?

Purpose is front-loaded, followed by report contents, a privacy note, and examples. No filler or redundancy given the complexity of an OpenFDA search tool; length is justified.

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?

No output schema exists, but the description covers report contents, search examples, and the masking quirk, giving enough for an agent to make a first call. It does not describe the exact response envelope (meta/results), which is a minor gap for a search tool.

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. The description enriches the parameters by showing dataset-specific search field examples (animal.species, original_receive_date, serious_ae) and listing count fields, going beyond the schema's generic query syntax.

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 ('Search') and a clear resource ('animal/veterinary adverse event reports'). The 'animal/veterinary' qualifier distinguishes it from sibling FDA event tools like fda_drug_events even without naming 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?

Provides clear context: reports of drug side effects in animals, and includes concrete example searches showing how to query species, date ranges, and serious events. Does not explicitly name alternatives or give when-not scenarios, so it stops short of a 5.

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

Deploy Server

Other Tools