Skip to main content
Glama

Measles Cases by State and Outbreak MCP

Measles cases history

measles_cases_history
Read-onlyIdempotent

US measles case history from CDC. view yearly (default): confirmed cases per year from 1985 to this year, with the highest and lowest year in the range. view weekly: cases per week by rash onset for one year (2022 on), monthly totals, the peak week and the recent trend.

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

Input Schema

NameRequiredDescriptionDefault
viewNoyearly (default) or weekly.
yearNoweekly: the year. Default the current year.
to_yearNoyearly: last year. Default the current year.
from_yearNoyearly: first year. Default 2000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world access, so the description's added value is the data provenance (CDC) and the effective coverage windows: 1985 to the current year for yearly, 2022 onward for weekly. Those bounds are real behavioral information the annotations do not supply, though permission, caching, and freshness behavior remain unstated.

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?

Two dense, front-loaded sentences: source first, then a parallel enumeration of yearly versus weekly outputs. Every clause carries information about return content, with no filler; only minor terseness in the enumerated lists keeps it from being flawless.

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 burden of describing returns and does so concretely (per-year cases, extremes, per-week cases, peak week, trend). Combined with 100% schema coverage and safety annotations, an agent has enough to call it correctly; only sibling differentiation is missing.

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, but the description adds effective data bounds that the schema does not: from_year has minimum 1900 yet data only starts in 1985, and weekly only applies from 2022 on. That clarifies which parameter combinations are actually meaningful, exceeding schema-level 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?

States the resource (US measles case history from CDC) and precisely enumerates the two output modes: yearly confirmed cases from 1985 onward with highest/lowest year, and weekly cases by rash onset from 2022 with peak week and trend. The purpose is unambiguous, but it never distinguishes itself from the sibling measles_cases_us, which by name sounds like an overlapping resource.

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?

Says which view is the default (yearly) and what each view produces, which implies choosing yearly for long-range trends and weekly for a single-year detail. It offers no explicit when-to-use/when-not guidance and no routing to the sibling tools, so the agent must infer the choice from the output descriptions.

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.