Skip to main content
Glama

ClinX open data: 340B and health centers

States with a 340B reporting law

reporting_states
Read-onlyIdempotent

The states whose law requires 340B reports, grouped by what the public can see: each filer's own report is posted; one state report gives a figure for each named entity; one state report gives totals only; or reports are required and none is public yet. For each state it gives what is public, where it stands, whether ClinX holds its figures, the page of figures on ClinX, and the official sources. Filter by state or by group.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOne group of states: own-reports, named-in-state-report, state-totals or not-posted-yet.
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

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent and closed-world behavior, so the bar is lower. The description adds real value beyond them by describing the four-group taxonomy and enumerating the per-state fields returned (public status, ClinX holdings, ClinX figures page, official sources), which matters since no output schema exists.

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 core concept, then the group taxonomy, then the return fields, then the filtering note. The ClinX phrasing ('whether ClinX holds its figures, the page of figures on ClinX') is slightly repetitive but carries information; overall it is tight and well ordered.

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 only two optional parameters, the description carries the burden of explaining what comes back, and it does so field by field. It stops short of noting ordering, counts, or typical result size, which would be the last remaining gap.

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 the baseline is 3, but the description goes further by explaining in prose what each group slug means (own report posted, one figure per named entity, totals only, not posted yet), giving the agent semantic grounding the identifier strings alone do not.

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 (states whose law requires 340B reports) and its organizing principle (grouped by what the public can see), then enumerates the four visibility categories. It is clearly distinguishable from data-retrieval siblings like get_law or find_laws, though it never explicitly names an alternative tool.

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

Usage Guidelines3/5

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

The only usage guidance is the closing 'Filter by state or by group,' which implies this is a browsable reference listing but gives no context on when to prefer it over state_overview or get_law. No when-not-to-use or preconditions are stated.

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.