Skip to main content
Glama

Query CDC Dataset

cdc.health.query
Read-onlyIdempotent

Query CDC health datasets (e.g., COVID deaths, chronic conditions) by state, year, age group, or condition. Filter with SoQL WHERE, SELECT, ORDER, GROUP BY. Returns structured rows with column names.

Instructions

Query a specific CDC dataset using SoQL filters — filter by state, year, age group, condition. Returns structured rows with column names. Supports WHERE, SELECT, ORDER, GROUP BY. Use cdc.datasets to find dataset IDs first (US Gov, Socrata SODA API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesCDC dataset ID in xxxx-xxxx format (e.g. "9bhg-hcku" for COVID deaths). Use cdc.datasets to find IDs.
whereNoSoQL WHERE clause filter (e.g. "state='CA'", "year > 2020", "age_group='65+'")
selectNoColumns to return, comma-separated (e.g. "state, year, deaths"). Default: all columns.
orderNoSort order (e.g. "year DESC", "deaths DESC"). Default: dataset default order.
groupNoGroup by columns for aggregation (e.g. "state" with select "state, SUM(deaths)")
limitNoMax rows to return (1-1000, default 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds value by stating it returns structured rows with column names and supports SoQL clauses, which goes beyond the annotations.

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?

The description is three clear, front-loaded sentences. It efficiently conveys the core purpose, supported operations, and a key prerequisite without extraneous information.

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?

With an output schema present, the description sufficiently covers return format ('structured rows with column names') and prerequisite (use cdc.datasets). All key aspects for a query tool are addressed.

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 the baseline is 3. The description adds minor value by mentioning SoQL clauses (WHERE, SELECT, ORDER, GROUP BY) which correspond to parameters, and giving examples of filters like state, year, age group, condition, but the schema already provides detailed examples.

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 clearly states the tool queries a specific CDC dataset using SoQL filters and mentions filtering by state, year, age group, condition. It distinguishes itself from the sibling tool cdc.health.datasets by instructing users to find dataset IDs first.

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?

The description explicitly instructs users to use cdc.datasets to find dataset IDs first, establishing a prerequisite. However, it does not explicitly mention when not to use this tool or provide alternatives beyond that.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server