CDC MMWR Reports

search_mmwr

Search MMWR articles by topic via PubMed.

Searches the Morbidity and Mortality Weekly Report journal for articles
matching your query. Use for finding CDC guidance, outbreak reports,
surveillance summaries, and public health recommendations.

Args:
    query: Search terms (e.g. 'COVID-19 vaccine effectiveness',
        'influenza surveillance', 'measles outbreak 2024').
    limit: Maximum number of results to return (default 20, max 100).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the PubMed source and gives example queries but does not mention read-only nature explicitly, rate limits, or other side effects. Adequate but could be richer.

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?

Well-structured and mostly concise, but the first two sentences are slightly redundant ('Search MMWR articles by topic via PubMed' vs 'Searches the Morbidity and Mortality Weekly Report journal...'). Args section is clear and earns its place.

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 simple tool (2 params, no annotations, output schema present), the description covers purpose, usage, and parameters adequately. It stops short of explaining result ordering or search semantics, but these are not critical given the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but the description's Args section fully explains both parameters with concrete examples (query) and constraints (limit default/max), going far beyond what the schema provides.

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 verb+resource ('Search MMWR articles by topic via PubMed') and clarifies scope (Morbidity and Mortality Weekly Report journal). Differentiates from sibling tools by focusing on free-text query search rather than surveillance data or report retrieval.

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?

Provides clear context with 'Use for finding CDC guidance, outbreak reports, surveillance summaries, and public health recommendations.' Does not explicitly name alternatives or exclusions, but clearly indicates this is for topic-based searching, distinguishing from siblings like get_recent_reports or get_report_detail.

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?