Skip to main content
Glama

Measles Cases by State and Outbreak MCP

Measles cases by state

measles_cases_by_state
Read-onlyIdempotent

Confirmed measles cases by state from CDC. With a state: its cases this year, last year and the year before, its rank, and its kindergarten MMR coverage. Without a state: every state ranked by cases this year and the states with none. New York City is reported separately from the rest of New York State; "NY" adds both.

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

Input Schema

NameRequiredDescriptionDefault
topNoHow many states to list in the summary when no state is given. Default 15.
yearNoYear, one of the last three. Default the current year.
stateNoState name or two-letter code, "New York City", "New York State" or "DC". Omit for all states.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds useful substance beyond that — the CDC source, the per-state payload contents, and the NYC/NY reporting quirk — but omits that the no-state mode is capped by the top parameter.

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 tight sentences, front-loaded with the resource and immediately branching into the with-state / without-state cases. Dense but nothing is wasted; the NYC note is placed last where it belongs.

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?

With no output schema, the description carries the return-shape burden and does so for both modes, and annotations cover the safety profile. The gap is the top parameter: the description says "every state" while the schema permits truncation to 15, which an agent could misread as a complete listing.

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 coverage is 100%, so the baseline is 3; the schema already documents state, year and top. The description does add real meaning for state (NYC counted separately, "NY" aggregates both) and implies year variance via "this year, last year and the year before", but says nothing about top's truncation behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Confirmed measles cases by state from CDC") and clearly describes two operating modes. It implicitly distinguishes itself from measles_cases_us by scoping to states, but it never names the national or historical siblings explicitly.

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 contextual guidance through its two-mode structure: pass a state for a single-state profile, omit it for a national ranking of states. No exclusions or named alternatives are given, so an agent must infer that measles_cases_us handles national totals.

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.