Skip to main content
Glama
Sign In

divux

by si.divux
OverviewDiscussionsAdmin

Illness: what's going around

check_illness
Read-only

Searches up to the latest 100 World Health Organization Disease Outbreak News reports for a country in the past 12 months, and discloses when the available reports cover a shorter period. For a US state, returns the latest available dated CDC figures: the state's acute respiratory illness level, wastewater levels for COVID, flu A and RSV at a typical site with the direction over three weeks (and the sites serving a county when one is given), and whether measles or H5 bird flu was found in the state's wastewater in the last four weeks. Inputs are a US state and an optional county, or a country. Applies to questions about current illness levels in a US state or reported outbreaks in a country. These are community levels, not a person's risk. Not medical advice. Travel-health notices for a destination are not in this result.

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

Input Schema

NameRequiredDescriptionDefault
stateNoUS state name or two-letter code, e.g. 'WA'
countyNoUS county name without 'County', e.g. 'King'
countryNoAny other country, for WHO outbreak reports; leave out for the US

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Any other country, for WHO outbreak reports; leave out for the US",
+  "maxLength": 60,
+  "type": "string"
+}
    • changedInput schema / properties / county / description
      Previous value: -"County name without 'County', e.g. 'King'"New value: +"US county name without 'County', e.g. 'King'"
    • removedInput schema / required
      Removed value: -[
-  "state"
-]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description goes well beyond by disclosing the 100-report cap, the 12-month window with self-reported truncation, the three-week wastewater direction, the four-week measles/H5 detection window, and data-source differences (WHO vs CDC). These are behavioral traits an agent cannot infer from the schema or annotations.

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?

Dense and front-loaded with substantive content, and every clause carries information about scope or return content. The long stacked sentences make the primary US-state path harder to scan than the WHO path listed first, but there is little outright waste.

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

Completeness5/5

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

No output schema exists, so the description must describe returns — and it does, naming the specific measures (illness level, COVID/flu A/RSV wastewater levels with direction, measles/H5 detection). With timeframe caveats and disclaimers included, an agent has everything needed to call it and interpret results.

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; the description adds real value with the conditional relationship between parameters — state plus optional county, or a country, and county only mattering in the state path. It does not add format or validation detail beyond schema (e.g., what a county yields when omitted), but it clarifies how the inputs combine.

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?

States specific verbs and resources: searches WHO Disease Outbreak News for a country, and returns CDC acute respiratory illness / wastewater figures for a US state. The two operating modes (state+county vs country) are distinguished explicitly, so an agent can tell exactly what it will get back.

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?

Gives clear applicability ("questions about current illness levels in a US state or reported outbreaks in a country") and useful exclusions (not personal risk, not medical advice, no travel-health notices). It stops short of naming a sibling such as check_trip for the travel-notice case, so routing is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All divux toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources