Skip to main content
Glama

Measles Cases by State and Outbreak MCP

US measles cases this year

measles_cases_us
Read-onlyIdempotent

Confirmed US measles cases for this year (or 2025) from CDC: the total, the number of outbreaks and the share of cases that are outbreak-associated, jurisdictions with cases, cases by age, vaccination status, percent hospitalized, deaths, the previous year for comparison and the trend over the last complete weeks.

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_us"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear. Default the current year. Full breakdowns exist for this year and last year; earlier years give the total only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the description's job is to add context, and it does by enumerating what the payload contains — totals, outbreak counts, share outbreak-associated, age breakdown, vaccination status, hospitalizations, deaths, prior-year comparison, and recent-week trend. What it omits is data recency: no mention of reporting lag or whether counts are provisional, which matters for CDC surveillance data.

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 and source are front-loaded in the first clause, followed by a compact enumeration of returned fields. It is a single dense sentence with no filler, though the long field list reads as a laundry list and could be grouped (e.g., counts vs. demographics vs. trend) for faster scanning.

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 correctly compensates by listing the return contents, which is the main thing an agent needs before calling. For a single optional-parameter read tool this is nearly sufficient; the only meaningful gap is freshness/cadence of the CDC data and whether figures are final or provisional.

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%, and the year parameter's schema already states the default and that earlier years return totals only. The description adds no syntax or format detail beyond that; it only reiterates the current-year focus and the presence of a prior-year comparison field. Baseline 3 is appropriate when the schema carries parameter meaning.

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?

The description names a specific resource and scope: "Confirmed US measles cases for this year (or 2025) from CDC", so an agent knows exactly what data it retrieves and the source. It doesn't name or contrast with the siblings (measles_cases_by_state, measles_cases_history, mmr_vaccination_rates), though the phrase "jurisdictions with cases" hints that per-state breakdown is included here rather than routed elsewhere.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the parenthetical "(or 2025)" and the bundled "previous year for comparison" suggest this is the default current-situation tool, but there is no explicit statement of when to prefer it over measles_cases_history or measles_cases_by_state. No exclusions or prerequisites are given, leaving the agent to infer routing from the sibling names alone.

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.