Skip to main content
Glama

ClinX open data: 340B and health centers

Find state 340B laws

find_laws
Read-onlyIdempotent

Search the state laws on the books that name the 340B program (not bills: laws already passed). Filter by state, kind, or words in the citation, title and summary.

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

Input Schema

NameRequiredDescriptionDefault
kindNoWhat the law does, for example contract-pharmacy, payer-nondiscrimination or reporting. about_the_data lists the kinds.
textNoWords to look for in the citation, title and summary.
limitNoHow many to return (default 20).
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

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered structurally. The description's own contribution is the data-scope distinction between enacted laws and bills, which is genuinely useful. It says nothing about result ordering, whether summaries are truncated, or how the default limit of 20 behaves, so the added behavioral context is modest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the most decision-relevant constraint (laws, not bills) parenthesized inline where it matters. Nothing could be removed without losing routing information.

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?

A read-only, four-parameter search tool with a fully documented schema and rich annotations; the description covers what it searches and how to narrow it. Missing only what an agent would want at call time, such as return ordering or result shape, which is a minor gap for a simple lookup.

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; the description edges slightly above by framing how the filters compose (state, kind, or words in citation/title/summary) and by pointing to about_the_data for the kind vocabulary, which the enum-less schema cannot convey. It adds no syntax or formatting detail beyond the schema itself.

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 (Search) and a specific resource (state laws naming the 340B program), and immediately rules out a confusable resource: "not bills: laws already passed." An agent can separate this from find_bills and get_law purely from the sentence.

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 sets the boundary against bill-searching ("not bills: laws already passed"), which is the main misuse risk for a sibling tool like find_bills. It also points to about_the_data for the list of valid kinds, which is real routing guidance. It does not, however, state when to call get_law instead of this search, so it stops short of full when/when-not coverage.

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.