CDC MMWR Reports

get_recent_reports

Get recent MMWR weekly reports and recommendations from CDC.

Returns the most recent Morbidity and Mortality Weekly Report articles
published by the CDC, including titles, publication dates, and PubMed IDs.
MMWR is the CDC's primary vehicle for scientific publication of timely,
reliable, and authoritative public health information.

Args:
    limit: Maximum number of reports to return (default 20, max 50).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are present, so the description must carry the behavioral disclosure burden. It does disclose that it returns the most recent articles, including specific fields (titles, dates, PubMed IDs), and states a default/max limit. However, it does not mention ordering, pagination, or any potential limitations about recency or availability. It is reasonably transparent for a simple read operation but lacks deeper context.

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 concise and well-structured. It opens with the action and resource, follows with return values, includes a brief background on MMWR (valuable context), and ends with parameter details. No unnecessary repetition or filler; every sentence contributes to understanding.

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 the tool's simplicity (one parameter) and the presence of an output schema (which covers return structure), the description is sufficiently complete. It explains what the tool does, what it returns, and parameter semantics. It could mention usage trade-offs with siblings, but that is covered in the usage guidelines dimension. Overall, the tool is well-specified for its purpose.

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?

The input schema only defines 'limit' with a default, but the description adds crucial semantics: 'Maximum number of reports to return (default 20, max 50).' This clarifies the meaning and constraints of the parameter, which the schema alone does not provide. Since there is only one parameter and it is fully explained, this is strong coverage.

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's function: 'Get recent MMWR weekly reports and recommendations from CDC.' It also specifies the output includes 'titles, publication dates, and PubMed IDs,' making the resource and action unambiguous. This distinguishes it from siblings like search_mmwr (search) and get_report_detail (single record detail).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention that search_mmwr should be used for searching specific topics, or that get_report_detail is for fetching a single report's details. Usage context is only implicit in the name and description.

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

All CDC MMWR Reports tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

The four tools have distinct purposes: search_mmwr finds articles by topic, get_recent_reports lists latest reports, get_report_detail fetches a specific article's details, and get_disease_surveillance specializes in surveillance data for a disease. There is slight overlap between get_disease_surveillance and search_mmwr, but the descriptions clarify that the former is disease-specific and returns surveillance data.

Naming Consistency4/5

The naming pattern is mostly consistent with get_ prefix for retrieval actions (get_recent_reports, get_report_detail, get_disease_surveillance) and search_mmwr for search. The suffixes vary (reports, detail, surveillance), which is acceptable but not perfectly uniform.

Tool Count5/5

With only 4 tools, the server is well-scoped for its purpose of providing MMWR report access. Each tool earns its place: search, recent list, detail retrieval, and disease-specific surveillance. No redundancy or excess.

Completeness4/5

The set covers the core workflow for MMWR reports: search, list recent, and get details. It also adds a specialized disease surveillance tool. A minor gap is the lack of full-text access, but abstract and metadata are sufficient for most use cases.

Resources

Need Help?