Skip to main content
Glama

ClinX open data: 340B and health centers

340B in one place

state_overview
Read-onlyIdempotent

A short picture of 340B law and legislation in one state (or US for Congress): how many laws are on the books and of what kind, how many bills name 340B and how far they have gone, which group of reporting states it is in (what the public can see of its 340B reports) and how many filed reports ClinX holds for it, and the next dates on the calendar, with links to the pages that hold the detail. With FED it gives the federal agencies instead: how many rules and notices name 340B, which are open for comment, and the next federal dates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "state_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state code such as RI or TX, US for Congress, or FED for federal agencies (rules and notices in the Federal Register).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, closed-world), so the added value here is the description of the composite payload shape and the fact that the response includes hyperlinks out to detail pages. It also discloses a useful provenance detail — that filing counts reflect only reports ClinX actually holds. With no output schema, this return-shape disclosure matters, though it stops short of stating empty-state or coverage-caveat behavior.

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?

Two sentences, front-loaded with the core purpose, and the FED exception is isolated cleanly at the end. The parenthetical '(what the public can see of its 340B reports)' is slightly clunky, but every clause carries real content about what is returned.

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 and a single required parameter, the description carries the burden of explaining return content, and it does so thoroughly across both the state and FED modes. An agent could decide whether this answers its question without opening anything else. Minor gap: no note on what appears when a state has no laws, bills, or reports.

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?

Only one parameter, and schema coverage is 100% with the accepted domain (two-letter code, US, FED) fully spelled out in the schema. The description restates the same US/FED semantics for the state argument without adding format, casing, or error-handling meaning. Baseline 3 applies since the schema does the work.

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 specific resource (340B law and legislation in one state) and enumerates exactly what the snapshot contains: law counts by kind, 340B-naming bills and their progress, reporting-state group, ClinX filing counts, and upcoming dates. It also carves out the FED variant as a different payload (federal rules and notices). It never names a sibling tool by name, so the differentiation from find_laws/find_bills/calendar 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 Guidelines4/5

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

Usage context is clear: this is the 'one place' aggregate view for a single state, with 'links to the pages that hold the detail' signaling that detail-seeking should go elsewhere. The FED branch condition is stated precisely. There are no explicit exclusions or named alternatives, which keeps it short of a 5.

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.