Skip to main content
Glama

CDC FluView weekly influenza-like illness and weighted ILI

health_fluview_influenza_cdc
Read-only

CDC FluView weekly influenza-like illness (ILI) and weighted ILI for the US or a region (served via Delphi Epidata, which mirrors CDC FluView): epiweek, ILI %, weighted ILI %, patient and provider counts. Give an epiweek range of up to 12 weeks. No outbreak maps. 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": {
      "region": "<region>",
      "epiweekFrom": "<epiweekFrom>",
      "epiweekTo": "<epiweekTo>"
    },
    "name": "health_fluview_influenza_cdc"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes'nat' for US national, or a state code like 'vt' (lowercase letters, 2 to 5 characters)
epiweekToYesLast epiweek, YYYYWW, at most 12 weeks after the first
epiweekFromYesFirst epiweek, YYYYWW, e.g. 202440

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
weeksNo
regionNo
sourceNo
checkedAtNo

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 declare readOnlyHint=true and openWorldHint=true, so safety is covered, and the description goes further by disclosing the data provenance (Delphi Epidata mirror of CDC FluView) and a concrete cost model: "$0.002 per successful call, paid with x402 ... failed calls are not charged." That billing and failure-charging detail is behavior an agent cannot get from the schema, though rate limits and pagination are unmentioned.

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 opening sentence front-loads the resource, provenance, and return fields, then appends constraints and pricing. Most sentences earn their place, though the pricing sentence is lengthy and slightly crowds the scoping information.

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?

For a three-parameter read tool with an output schema and full schema coverage, the definition supplies data source, scope limits, and cost, which is sufficient to call it correctly. Return values are described despite the output schema existing, which is redundant but harmless; missing only rate-limit or failure-mode detail.

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%, with region ('nat' or a 2-5 letter state code), epiweekFrom (YYYYWW), and epiweekTo (at most 12 weeks after the first) all documented. The description restates only the 12-week span, duplicating the schema rather than adding format or edge-case meaning, so the baseline 3 applies.

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 the specific resource and provenance ("CDC FluView weekly influenza-like illness (ILI) and weighted ILI", "served via Delphi Epidata, which mirrors CDC FluView") and enumerates the returned measures (epiweek, ILI %, weighted ILI %, patient and provider counts). It also draws a scope boundary with "No outbreak maps." It stops short of naming a sibling tool to contrast against, so it is clear but not fully differentiated.

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 implied by the constraint "Give an epiweek range of up to 12 weeks" and the exclusion "No outbreak maps," which tells the agent this is not a geospatial/outbreak-mapping source. However, there is no explicit when-to-use guidance, no mention of when a different dataset or sibling would be preferable, and no prerequisites beyond the payment note.

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