Skip to main content
Glama

CDC/NCHS leading causes of death by US state and year

health_cdc_wonder_mortality
Read-only

CDC/NCHS leading causes of death by US state and year (data.cdc.gov open data): cause, deaths and age-adjusted death rate per 100,000. Published table only, not the CDC WONDER query tool. Up to 50 rows per call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "health_cdc_wonder_mortality"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many rows, 1 to 50 (default 10)
yearNoFour-digit year, optional
stateYesUS state name as in the dataset, e.g. Vermont, 2 to 40 letters and spaces

Output Schema

NameRequiredDescriptionDefault
yearNo
stateNo
causesNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description's additions carry real weight: a hard 50-rows-per-call cap and a pay-per-call model ($0.002, x402/USDC on Base, Solana and others, with failed calls uncharged). That cost and payment prerequisite is exactly the kind of thing an agent cannot infer from structure. It still omits ordering behavior and what the response looks like when a state/year is unavailable.

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?

The core capability is front-loaded in the first sentence and the exclusion follows immediately. The pricing sentence is longer than it needs to be given the enumeration of networks, but it is still a single tight sentence with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a paid, capped query tool the description leaves two operational questions open: how to retrieve more than 50 rows and what the default behavior is when 'year' is omitted. Adequate but with clear gaps.

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 state format, the 1-50 range and the optional four-digit year are already documented. The description only reinforces the 50-row ceiling ('Up to 50 rows per call') and adds no meaning about what happens when 'year' is omitted or how 'max' interacts with available data. Baseline 3 is appropriate.

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?

Names a concrete resource (CDC/NCHS leading causes of death by US state and year), the source (data.cdc.gov), and the returned fields (cause, deaths, age-adjusted death rate per 100,000). It also fences off a commonly confused alternative ('Published table only, not the CDC WONDER query tool'), though it offers no explicit verb and does not differentiate against the listed sibling datasets.

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?

The negative scoping ('not the CDC WONDER query tool') tells the agent what this is not, which is useful, but there is no positive guidance on when to pick it over the other health data siblings or what to do when the state/year pair has no data. Usage is implied by the subject matter rather than stated.

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.

Resources