Skip to main content
Glama

Measles Cases by State and Outbreak MCP

Kindergarten MMR vaccination rates

mmr_vaccination_rates
Read-onlyIdempotent

Kindergarten MMR vaccination coverage (2 doses) from CDC. With a state: its rate for the latest or a given school year, its rank, the change since 2019-20 and the trend. Without a state: every state ranked from lowest, how many are below the 95% herd immunity target, and the state median. School years 2009-10 to the latest.

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

Input Schema

NameRequiredDescriptionDefault
stateNoState name or code, "New York City" or "Houston". Omit for all states.
school_yearNoSchool year such as 2025-26 (or 2025). Default the latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value on top by disclosing the returned content (rate, rank, change since 2019-20, trend; or national ranking, count below the 95% target, median) and the data vintage. It does not clarify ambiguous details such as what direction the rank runs in single-state mode.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing distinct work: source and metric, single-state output, all-state output, then the temporal scope. The with/without framing is front-loaded and there is no filler.

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 must carry return-shape burden, and it does so for both calling modes plus the available date range. The only gap is the unspecified ordering of the single-state rank and how the 'change since 2019-20' is expressed, which an agent might want before interpreting results.

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 still adds meaning the schema lacks: it spells out the contrasting behaviors of supplying vs. omitting `state`, and it bounds `school_year` to 2009-10 through the latest, a valid range the schema does not state.

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 metric, population, and source: kindergarten MMR coverage (2 doses) from CDC. The two-mode split (with vs. without a state) makes it immediately distinguishable from the sibling measles_cases_* tools, which measure case counts rather than coverage rates.

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?

Explicitly explains what each parameterization yields: 'With a state: its rate... its rank... Without a state: every state ranked from lowest...' That is clear routing guidance for the two calling modes. It stops short of naming alternatives or stating exclusions, so it does not reach 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.