Skip to main content
Glama

ClinX open data: 340B and health centers

One federal rule or notice in full

get_notice
Read-onlyIdempotent

Everything the table holds about one federal rule or notice, by its notice_id from find_notices (its Federal Register citation, such as 91 FR 48883, also works): the kind of document, the agency that wrote it, what it does about 340B in a sentence, the Federal Register's own words about its dates, the days it sets, the passage that names 340B, and links to the official page and the printed PDF.

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": {
      "notice_id": "<notice_id>"
    },
    "name": "get_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
notice_idYesFor example fr-2026-15633.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety context is covered. The description contributes beyond them by disclosing the shape of the payload (an enumerated set of fields including quotation of the Federal Register's own language and PDF/HTML links), which matters because there is no output schema. It does not mention behavior on a missing notice_id, but the gap is minor.

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 that opens with the scope and then lists the returned components; every clause carries information and nothing repeats the title. It is a long run-on enumeration, slightly harder to scan than a short lead plus list, but no wording is wasted.

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?

For a one-parameter read-by-id tool with no output schema, the description carries the return-value burden well by enumerating what comes back and by documenting an alternate identifier format. The only omission is behavior on a nonexistent id, which is secondary for this tool's complexity.

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 adds genuinely new meaning: the key may be either the notice_id or the Federal Register citation (e.g., '91 FR 48883'), which the schema does not mention at all. That single addition is what an agent most needs to avoid a failed lookup.

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+resource ('everything the table holds about one federal rule or notice') and enumerates exactly what that record contains — document type, agency, 340B effect, dates, day counts, 340B passage, and links. The reference to 'notice_id from find_notices' implicitly distinguishes it from the search sibling without needing to open either 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?

Makes clear this is the retrieval step following find_notices, and tells the agent which key to supply. It does not spell out an explicit when-not-to-use case (e.g., that it returns nothing for an unknown id, or that find_notices is the tool for discovery), but the context is unambiguous for a lookup-by-id tool.

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.