Skip to main content
Glama

Meps Drugs For Condition

meps_drugs_for_condition
Read-onlyIdempotent

Which prescription drugs Americans actually take for a given medical condition, with a national estimate of how many people take each one. Covers the whole US population, every payer, every age, commercial and uninsured included, not just Medicare or Medicaid. Ask with a plain condition name like "depression", "high cholesterol", "type 2 diabetes" or "asthma". Returns drugs ranked by estimated people treated, each with the survey sample behind it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "condition": "depression"
    },
    "name": "meps_drugs_for_condition"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoSurvey year. Defaults to the most recent loaded.
limitNoMax drugs, default 20, max 100.
conditionYesCondition in plain words ("depression", "high blood pressure"), or a CCSR category code like MBD002.
min_sampleNoMinimum survey respondents behind a row, default 60AHRQ's own reliability floor. Lower it to see less-common drugs, which come back marked reliable:false because AHRQ would not publish them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / min_sample / description
      Previous value: -"Minimum survey respondents behind a row, default 60 — AHRQ's own reliability floor. Lower it to see less-common drugs, which come back marked reliable:false because AHRQ would not publish them."New value: +"Minimum survey respondents behind a row, default 60AHRQ's own reliability floor. Lower it to see less-common drugs, which come back marked reliable:false because AHRQ would not publish them."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add context — and it does: population coverage (whole US, all payers, commercial and uninsured, not just Medicare/Medicaid) and the return ordering (drugs ranked by estimated people treated, each with its survey sample). It stops short of stating result limits or what happens when a condition name matches nothing.

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?

Four sentences, front-loaded with the core question the tool answers, then scope, then input format, then return shape. The payer/age enumeration is slightly padded ("commercial and uninsured included, not just Medicare or Medicaid") but it does real disambiguation work for a survey dataset.

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?

There is no output schema, so the description carries the return-value burden and does so adequately by explaining ranking, the estimate, and the per-row survey sample. Combined with annotations and a fully documented input schema, an agent has enough to call this correctly; only failure/empty-result behavior is unaddressed.

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 description coverage is 100%, so all four parameters including year, limit, min_sample, and condition are already documented in the schema, including the CCSR code alternative and the AHRQ reliability floor. The description adds only the plain-language example phrasing for condition, which the schema also covers, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (prescription drugs) and a concrete query direction (given a medical condition), plus the metric returned (national estimate of people taking each drug). That implicitly separates it from the inverse sibling meps_conditions_for_drug, but no sibling is named, so the differentiation is inferential rather than explicit.

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?

Usage guidance is about input phrasing ("Ask with a plain condition name like 'depression'") rather than about when to pick this tool over meps_top_drugs or meps_drug_use. There are no exclusions or stated prerequisites, and the population-scope sentence ("every payer, every age") hints at when this dataset is appropriate without saying so directly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.