Skip to main content
Glama
mymedi-ai-mcp-server

mymedi-ai-mcp-server

by MyMedi-AI

Disease surveillance case counts (CDC NNDSS)

disease_surveillance
Read-only

Retrieve CDC weekly notifiable disease data including case counts and trends filtered by condition, ICD-10 code, or state.

Instructions

Look up disease surveillance data including case counts and trends by condition and geography. Source: CDC National Notifiable Diseases Surveillance System (NNDSS) weekly data on data.cdc.gov.

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

Input Schema

NameRequiredDescriptionDefault
codeNoICD-10 code (auto-mapped to condition name)
stateNo2-letter state code to filter by geography
conditionNoDisease or condition name (e.g., "Hepatitis A", "Salmonellosis")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.9
    • addedInput schema / properties / code / maxLength
      Added value: +500
    • addedInput schema / properties / condition / maxLength
      Added value: +500
    • addedInput schema / properties / state / maxLength
      Added value: +500
  2. Addedv1.2.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by naming the upstream source (CDC NNDSS weekly data on data.cdc.gov), which conveys provenance and update cadence. However, it says nothing about behavior with zero filters (only three optional parameters), result volume, or limits, which matters for an open-world lookup.

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?

Two sentences, front-loaded with the capability and closing with the data source. No filler or restated title text.

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?

Given three simple optional parameters and no output schema, the description supplies the essential framing plus provenance. It is slightly incomplete in not addressing the all-optional call case (what an unfiltered query returns) or result granularity, but nothing critical is missing for a read-only lookup.

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 each parameter is already documented in the schema, and the baseline of 3 applies. The description's 'by condition and geography' mildly echoes the condition and state filters but never mentions the ICD-10 code auto-mapping parameter, so it adds no meaning 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?

Specific verb (look up) plus specific resource (disease surveillance data, case counts and trends) and named scope (condition, geography). The CDC NNDSS source identifier makes it unambiguous against every sibling, none of which touch surveillance data.

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 'by condition and geography' phrasing implies how to call it, but there is no explicit when-to-use guidance, no statement of when to use this instead of code_lookup or ner_extract, and no explanation of whether filters are combinable or optional. The agent must infer usage from the parameter list.

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