Skip to main content
Glama

ClinX open data: 340B and health centers

340B calendar

calendar
Read-onlyIdempotent

Dated events for 340B bills and federal notices: each bill's steps (introduced, sent to committee, votes, signed, vetoed, became law), the days a state's 340B report is due (report due), hearings that name a listed bill, the days legislative sessions start and end, and for federal agencies (state FED) the day a rule or notice was published, the day its comments close, the day it takes effect and other days it sets. With no dates given it returns what is coming up from today, soonest first. Give from and to for a past stretch. Dates can move: check the official page before planning around one.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day, year-month-day.
fromNoFirst day, year-month-day. Default: today.
kindNo
limitNoHow many to return (default 20).
stateNoTwo-letter state code such as RI or TX, US for Congress, or FED for federal agencies (rules and notices in the Federal Register).
bill_idNoOnly this bill's dates.
notice_idNoOnly this federal rule's or notice's dates, for example fr-2026-15633.

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description nonetheless adds real behavioral detail beyond them: the default window starting today, the soonest-first ordering, and the warning that dates can shift before planning around them. It stops short of covering result size behavior beyond the schema's limit field.

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?

The long first sentence is dense but every clause names a distinct event type that the agent needs in order to pick the right kind values. The default-behavior and date-caveat sentences are short and useful. Slightly heavy enumeration, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven parameters and no output schema, the definition should say more about what a returned event looks like beyond it being a dated event tied to a bill or notice. It covers scope, defaults, ordering and caveats well, but leaves the result shape entirely implicit for a tool whose whole purpose is returning records.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 86%, so the schema already carries most parameter meaning, including the from default and the state pattern. The description adds only a little on top — chiefly that state 'FED' means federal agencies and Federal Register rules/notices, which contextualizes the kind enum values like 'comments close' and 'takes effect'. That is marginal value over an already well-documented schema.

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 opens with a specific resource ('Dated events for 340B bills and federal notices') and then enumerates the exact event classes covered — bill steps, report-due days, hearings, session start/end, and Federal Register notice milestones — which makes the scope unmistakable. It does not explicitly contrast itself with siblings like find_bills or get_bill, so an agent must infer that those return entities while this returns dated events.

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?

Usage context is stated clearly: with no dates it returns upcoming events from today, soonest first, and passing from/to retrieves a past stretch. What's missing is explicit routing against alternatives (e.g. 'use get_bill for the bill's text, this only for its dates'), so the agent gets context but no exclusions.

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.