Skip to main content
Glama

ClinX open data: 340B and health centers

Find health centers

find_health_centers
Read-onlyIdempotent

Search the federally funded health centers (community health centers that hold a Health Center Program grant from HRSA) whose yearly reports to HRSA are held by ClinX. Filter by state, by words in the name, city, key or grant number, or by a year the health center reported. Returns short rows: key, grant number, name as HRSA prints it, city, state, the years held, kinds of funding, urban or rural, the number of sites listed, and the ClinX page. The rows are in the order of the names. Use get_health_center_report for what one health center reported. The answer says which states are held so far.

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

Input Schema

NameRequiredDescriptionDefault
textNoWords to look for in the name (this year's or an earlier one), the city, the key or the grant number.
yearNoOnly health centers with a report for this year, such as 2025.
limitNoHow many to return (default 20).
stateNoTwo-letter state code such as RI or MA.

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 readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds real behavioral context beyond them: the dataset is limited to centers whose reports ClinX holds, rows come back ordered by name, fields are 'short rows' rather than full reports, and the response also reports which states are covered. It stops short of describing result counts or pagination behavior for the limit.

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?

Front-loaded with the resource definition, then filters, then return shape, then the routing pointer — a sensible order. It is a dense single block with a long parenthetical, but nearly every clause carries information an agent needs; only the return-field enumeration could be trimmed slightly.

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?

No output schema exists, yet the description enumerates the returned fields and their ordering, and it discloses the coverage limitation of the underlying data. With annotations and full schema coverage in place, the remaining gap is minor detail on result counts or default ordering behavior with the limit parameter.

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 the four parameters are already documented, including the text-search targets and the year semantics. The description largely restates those filters at a higher level and adds no new syntax or edge-case guidance, so the baseline 3 applies.

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?

Starts with a specific verb and a precisely bounded resource: federally funded health centers holding an HRSA Health Center Program grant whose yearly reports are held by ClinX. The scope qualifiers and the sibling pointer make it impossible to confuse with get_health_center_report or the other find_* tools.

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

Usage Guidelines5/5

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

Explicitly states the alternative for a related need: 'Use get_health_center_report for what one health center reported.' Combined with the stated filters and the row-level summary return, an agent can decide between search and detail lookup without opening either schema.

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.