Skip to main content
Glama

ClinX open data: 340B and health centers

One 340B bill in full

get_bill
Read-onlyIdempotent

Everything the table holds about one bill, by its bill_id from find_bills: sponsor, stage, latest step in the legislature's own words, the passage that names 340B, links to the official page and text, and its dated steps.

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": {
      "bill_id": "<bill_id>"
    },
    "name": "get_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
bill_idYesFor example ri-2025-h5634 or us-119-hr4581.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds the genuinely useful behavioral detail that with no output schema present, the returned payload spans sponsor, stage, verbatim latest step, the 340B passage, official links and dated steps — telling the agent exactly what one call yields.

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?

One front-loaded sentence leads with the scope ('Everything the table holds about one bill'), then the key, then the field list. The enumeration is long but earns its place because no output schema exists; only minor tightening would improve it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single required parameter, full schema coverage and no output schema, the only real gap would be return content — and the description explicitly inventories it. Nothing an agent needs in order to call this correctly is missing.

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% and the schema already supplies example IDs, so a baseline of 3 applies. The description goes slightly beyond by identifying the provenance of bill_id (find_bills), which tells the agent where a valid value must come from rather than guessing at the format.

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?

The description names a specific retrieval ('Everything the table holds about one bill') keyed by a specific identifier, and distinguishes itself from the list-style sibling find_bills by pointing at it as the ID source. An agent can tell this is the detail/fetch counterpart to search without opening the 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?

It clearly establishes the prerequisite workflow: call this with a bill_id obtained from find_bills, which routes the agent to the right sibling first. It stops short of explicit exclusions (e.g., 'do not use for searching by sponsor/keyword'), so a 4 rather than 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.