Skip to main content
Glama

ClinX open data: 340B and health centers

Find filed 340B reports

find_filings
Read-onlyIdempotent

Search the reports that covered entities and states have filed about 340B, which the Scorecard holds. Filter by state, year, entity name or 340B ID, entity type, kind of record (an entity's own filing, a row a state printed about an entity, a state's totals) or form. Returns short rows: the entity, state, year, form, kind of record, the ClinX page and the official source. Use get_filing for one report in full. Figures are exactly as filed and ClinX ranks no one.

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_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNoThe form's id, as listed by about_the_data.
yearNoThe reporting year, such as 2025.
limitNoHow many to return (default 20).
stateNoTwo-letter state code such as RI or TX. Use US for Congress.
entityNoWords in the entity's name as filed or in HRSA's name for it (Ohio's workbooks print an ID and no name), or its city, or a 340B ID such as DSH410009.
entity_typeNoFor example hospital, health_center or state_total. about_the_data lists the types held.
record_kindNoFor example filing (an entity's own report), state_report_row (a row a state printed about an entity) or state_report_totals. about_the_data lists the kinds held.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower. The description adds substantive context beyond them: results are 'short rows' rather than full reports, and the 'figures are exactly as filed and ClinX ranks no one' caveat tells the agent the data is uninterpreted source material.

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?

Three sentences, front-loaded with the search scope, then the filter axes, then the return shape and sibling pointer. Dense but every clause carries information; no filler.

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?

With no output schema, the description compensates by naming the returned fields (entity, state, year, form, record kind, ClinX page, official source). Combined with the get_filing referral, an agent has enough to call it correctly; only pagination edge behavior is left implicit.

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 100%, so baseline is 3, but the description adds conceptual meaning the schema doesn't: it glosses the three record_kind values ('an entity's own filing, a row a state printed about an entity, a state's totals') and clarifies that entity may be a name, city, or 340B ID.

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 and resource ('Search the reports ... filed about 340B') and names the exact scope (entity filings, state rows, state totals) so the agent can distinguish it from get_filing immediately.

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?

Explicitly routes the agent to get_filing when one full report is needed, and enumerates the filter axes that select this tool. It stops short of stating when NOT to search or what happens with zero filters, but the selection context is clear.

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.