Skip to main content
Glama

ClinX open data: 340B and health centers

Health center funding dates

health_center_calendar
Read-onlyIdempotent

Dated lines for health center funding: for each HRSA funding opportunity on Grants.gov the day its notice is expected, the day applications are due and the day awards are expected, and for Federal Register documents that name the Health Center Program the day comments close and the day it takes effect. With no dates given it returns what is coming up from today, soonest first. Give from and to for another stretch. Each line says whether the date is HRSA's estimate. This is a separate calendar from the 340B one (the calendar tool).

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

Input Schema

NameRequiredDescriptionDefault
toNoLast day, year-month-day.
fromNoFirst day, year-month-day. Default: today.
kindNo
textNoWords to look for in the title.
limitNoHow many to return (default 20).
sourceNogrants.gov for funding opportunities, federal register for rules and notices.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 beyond them -- the default rolling window starting today, the soonest-first sort order, and the flag on each line indicating whether a date is HRSA's estimate rather than a confirmed date. It does not mention truncation/limit behavior or the return envelope, but the added context is substantive.

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?

Purpose and data sources come first, then default behavior, then the estimate caveat, then sibling differentiation -- a sensible front-loaded order with each sentence carrying information. The opening sentence is long and clause-heavy, but nothing is filler.

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 six-parameter, no-output-schema read tool, the description covers what the tool returns (dates plus an estimate indicator), default windowing, ordering, and which upstream sources it draws from. Filtering semantics for text/source/limit are left to the schema, which documents them adequately, so an agent has enough to call it correctly.

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 coverage is 83%, so the schema already documents to, from, text, limit, and source, and the description largely restates the from/to window semantics rather than adding syntax or edge-case meaning (e.g. what happens if only 'to' is supplied). Its one genuine semantic contribution is enumerating the date kinds that the 'kind' parameter filters on and the estimate-vs-confirmed distinction per line.

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 states a specific resource and verb-domain -- dated lines for health center funding -- and enumerates the exact date kinds emitted for both HRSA/Grants.gov opportunities and Federal Register documents naming the Health Center Program. It also explicitly separates itself from the sibling 'calendar' tool (the 340B calendar), so an agent can disambiguate without opening a 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?

It clearly states the default invocation behavior ('With no dates given it returns what is coming up from today, soonest first') and how to widen the window ('Give from and to for another stretch'), plus which sibling it is not. It does not, however, say when to prefer this over find_funding_opportunities or find_notices, so usage context is clear but not fully routed.

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.