Skip to main content
Glama

COVID, Flu and RSV Wastewater Levels MCP

COVID, flu and RSV wastewater levels in a county

covid_flu_rsv_levels_county
Read-onlyIdempotent

Wastewater levels for COVID-19, flu and RSV at every CDC sewershed site that serves a county: each site's level and category for the latest week, the readings for the last weeks (default 6, up to 12) and the population served. If no site serves the county, lists the counties in the state that have one.

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": {
      "county": "<county>",
      "state": "<state>"
    },
    "name": "covid_flu_rsv_levels_county"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesState name or two-letter code.
weeksNoWeeks of history per site. Default 6.
countyYesCounty name, e.g. "Cook", "Los Angeles County", "St. Louis" or "Orleans Parish".
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.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld access, so safety is covered. The description adds useful behavior beyond that: the default of 6 weeks with a cap of 12, the fact that results are per-site rather than aggregated, and the empty-result fallback. It does not say how levels are expressed (units, percentile basis) or what ordering to expect, 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.

Conciseness4/5

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

One dense sentence front-loads the resource and scope, then appends the fallback behavior. There is no filler, though the sentence packs several clauses and could be split for faster scanning.

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 takes on the job of explaining returns and does so at the field level: level, category, prior weeks, population served. The fallback behavior rounds it out. It stops short of describing units or how 'category' is defined, which leaves a small gap for an agent interpreting the values.

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%, and the schema already documents state formats, county examples, the weeks default and range, and the pathogen enum values. The description restates the 6-to-12 week default but adds no new meaning for county or pathogen beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 states a specific resource (wastewater levels for COVID-19, flu and RSV) at a specific granularity (every CDC sewershed site serving a county) and spells out what each record contains: level, category, recent readings, and population served. That level of specificity clearly separates it from the national, state, and compare_states siblings.

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?

County-level scope is explicit and the fallback path is documented: if no site serves the county, it returns the in-state counties that do have coverage. That gives an agent a clear condition for choosing this tool. What is missing is any explicit instruction naming the state or national sibling as the better choice when county granularity is not needed.

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.