Skip to main content
Glama

ClinX open data: 340B and health centers

Find 340B bills

find_bills
Read-onlyIdempotent

Search the bills in Congress and the state legislatures that name the federal 340B drug pricing program. Filter by state, stage, role (main: the bill is about 340B; part: a wider bill with a 340B provision; mention: names it in passing), kind, or words in the title, number or summary. Newest activity first.

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

Input Schema

NameRequiredDescriptionDefault
kindNoWhat the bill does about 340B.
roleNo
textNoWords to look for in the bill number, title and summary.
limitNoHow many to return (default 20).
stageNoHow far the bill has gone. Did not pass means the bill ended without becoming law: it is finished and nothing is pending.
stateNoTwo-letter state code such as RI or TX. Use US for Congress.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds one genuine behavioral fact beyond them — results are ordered by newest activity first — and clarifies the role taxonomy. It does not say how results are shaped, whether there is pagination, or how the text match works, so with annotations carrying the safety profile a 3 is appropriate.

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?

Three sentences: scope first, filter surface second, ordering last. No filler, and the inline parenthetical for role is placed where it is needed rather than in a separate paragraph.

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, yet the description covers scope, all six filters at least by name, and sort order — enough to call it correctly. It stops short of describing result fields or result-volume behavior, which is the only real gap for a six-parameter search tool.

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?

Schema coverage is 83%, so the baseline is 3, but the description earns an upgrade by defining the three role values (main = bill is about 340B; part = wider bill with a 340B provision; mention = named in passing), which the schema leaves as a bare enum. It also confirms text searches the number, title and summary. State, stage, kind, and limit are left to 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?

States a specific verb ("Search") and a precisely bounded resource: bills in Congress and state legislatures that NAME the federal 340B program. The scope word "name" plus "bills" (as opposed to laws or filings) makes it separable from siblings like find_laws and find_filings without opening a schema.

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?

Gives clear when-to-use context: retrieve bills that mention 340B, narrowed by state, stage, role, kind, or text. It does not explicitly exclude cases or point at a complement (e.g., use get_bill for a single known bill), so the agent must infer that boundary from sibling names.

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.