Skip to main content
Glama

COVID, Flu and RSV Wastewater Levels MCP

COVID, flu and RSV levels in a state

covid_flu_rsv_levels_state
Read-onlyIdempotent

CDC wastewater viral activity levels for COVID-19, flu (influenza A) and RSV in one US state, DC or territory for the latest week: how many sewershed sites are Very Low, Low, Moderate, High or Very High, the share of people served by High or Very High sites, the median site level and the change from the week before, a 6-week trend, and the state's emergency department acute respiratory illness level.

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

Input Schema

NameRequiredDescriptionDefault
stateYesState name or two-letter code, e.g. "Ohio" or "OH". DC, Puerto Rico and territories also work.
pathogenNocovid (SARS-CoV-2), flu (influenza A), rsv, or all. Default all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds what annotations cannot: the upstream data source (CDC wastewater), the temporal window (latest week plus a 6-week trend), and the specific measurements returned. It stops short of noting data-refresh cadence or behavior for stale or missing state data, which keeps it from a 5.

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?

A single front-loaded sentence that opens with the data source and scope before listing returned metrics. Every clause corresponds to something an agent or its caller would want to know, and nothing is redundant.

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 carries the burden of describing return content, and it does so thoroughly across all metrics. Minor gaps remain: the units or scale of 'median site level' and the week-over-week change are unstated, as is behavior for invalid or ambiguous state inputs.

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%, with both parameters fully described including the enum values and the 'all' default, so the baseline is 3. The description confirms the pathogen scope (COVID-19, flu/influenza A, RSV) and geographic reach (state, DC, territory), but adds no format guidance or examples beyond the schema.

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?

The description names a specific resource (CDC wastewater viral activity levels for COVID-19, flu and RSV), a precise scope (one US state, DC or territory, latest week), and enumerates the exact fields returned. The phrase 'in one US state' implicitly separates it from the county and national siblings without needing to name them.

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: 'for the latest week' tells the agent this is the current-snapshot tool rather than a historical query, and 'one US state' hints at the geographic scope. There is no explicit statement of when to prefer this over covid_flu_rsv_levels_county, the national tool, or the compare tool, and no stated prerequisites or exclusions.

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.