Skip to main content
Glama

ClinX open data: 340B and health centers

One state 340B law in full

get_law
Read-onlyIdempotent

Everything the table holds about one state law, by its law_id from find_laws: citation, who it binds, what it limits, how it is enforced, dates, the passage that names 340B and the link to the official text.

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": {
      "law_id": "<law_id>"
    },
    "name": "get_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
law_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/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 the safety profile is covered. The description adds useful substance beyond that by listing what the record contains (citation, binding scope, limits, enforcement, dates, the 340B passage, official-text link), though it says nothing about behavior for an invalid or missing law_id.

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?

One front-loaded sentence: resource and lookup key come first, then the payload enumeration. No filler, no restating of the title, and the field list earns its place because there is no output schema.

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 no output schema, the description carries the return-value burden and does so by enumerating the record's contents. The lookup key's origin is explained and the single-parameter surface is fully covered, leaving nothing an agent needs before calling it.

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 0% – law_id is documented only as a bare string. The description compensates by identifying the parameter's provenance ('from find_laws'), telling the agent where a valid value comes from rather than just its type. That is meaningful added semantics over an undescribed string field.

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 retrieval verb and resource ('Everything the table holds about one state law') and names the key ('by its law_id'), which cleanly separates it from the search sibling find_laws. The enumeration of returned fields further pins down what the tool actually yields.

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?

The phrase 'by its law_id from find_laws' tells the agent that this tool is the second step in a find-then-fetch flow, which is a concrete usage cue rather than an implied one. It stops short of stating exclusions or what to do when the ID is unknown, so it is strong but not exhaustive.

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.