Skip to main content
Glama

ClinX open data: 340B and health centers

Find federal 340B rules and notices

find_notices
Read-onlyIdempotent

Search the rules, proposed rules and notices that federal agencies have published in the Federal Register since January 2025 and that name the 340B program. Filter by type, role (main: the document is about 340B; part: a wider document with a part on 340B; mention: names it in passing), whether comments are still open, the day it was published, or words in the title, citation, agency, docket and summary. Newest first.

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

Input Schema

NameRequiredDescriptionDefault
toNoPublished on or before this day, year-month-day.
fromNoPublished on or after this day, year-month-day.
roleNo
textNoWords to look for in the title, citation, document number, agency, docket and summary.
typeNoThe Federal Register's kind of document. Rule is a final rule.
limitNoHow many to return (default 20).
open_for_commentNoTrue for documents whose last day for public comments has not passed.

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real behavior: a hard corpus boundary of 'since January 2025', the meaning of the role tiers, and the default sort order 'Newest first'. It does not mention result volume beyond the schema's limit parameter or pagination behavior, which is a minor omission.

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 tight opening sentence carries the corpus, the filters and the filter semantics, followed by a two-word 'Newest first' for ordering. Scope is front-loaded and nothing is redundant, despite the density.

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 seven optional parameters and no output schema, the description supplies enough for a correct call: the domain boundary, all filter dimensions and the sort order. The remaining gap is the shape of a returned notice (fields like citation, docket or publication date that a follow-up get_notice call might need), which the agent must infer.

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 86%, so a 3 would be the baseline; the description earns more by unpacking the role enum — 'main' vs 'part' vs 'mention' — which the schema lists as bare values with no per-value documentation. It also clarifies that the text filter spans title, citation, agency, docket and summary, matching and reinforcing the parameter rather than merely restating it.

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 opens with a specific verb and resource — search rules, proposed rules and notices published in the Federal Register since January 2025 that name 340B — and pins down the corpus scope with a date floor. That scope, plus the fact it is a search rather than a fetch, clearly separates it from siblings like find_laws, find_bills and get_notice.

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 makes the use case clear ('search ... that name the 340B program') and enumerates the dimensions you can narrow by, which implicitly tells the agent when this tool applies. It stops short of explicit routing guidance — it never says to use get_notice to open a specific document or find_health_centers for provider-level questions — so no exclusions 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.