Skip to main content
Glama

ClinX open data: 340B and health centers

Find HRSA funding opportunities for health centers

find_funding_opportunities
Read-onlyIdempotent

Search the funding opportunities HRSA (the federal agency that funds health centers) lists on Grants.gov, both forecasts and posted notices. Filter by words in the title, number or description, to the Health Center Program's own opportunities, by status, or to those open for applications on a day. Returns short rows with the application due date as published (and whether it is HRSA's estimate), amounts as published, the Grants.gov page and the ClinX page, soonest due date first. Give opportunity (a number such as HRSA-27-006) for one in full, with its description, who can apply and every date.

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

Input Schema

NameRequiredDescriptionDefault
textNoWords to look for in the title, the opportunity number and the description.
limitNoHow many to return (default 20).
statusNoforecasted: HRSA plans to publish it, dates are estimates. posted: the notice is published.
open_onNoOnly notices posted on or before this day whose applications are due on or after it, year-month-day. A forecast is not open.
opportunityNoOne opportunity in full, by its number (for example HRSA-27-006) or its Grants.gov id (for example 363419).
health_center_programNoTrue for only the opportunities HRSA files under the Health Center Program itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description focuses on behavior that annotations cannot convey: rows are short, the due date is 'as published' with an HRSA-estimate caveat, amounts are as published verbatim, both the Grants.gov and ClinX links are returned, and results are ordered soonest-due first. Detail mode additionally discloses which fields come back (description, who can apply, every date). Nothing here contradicts the readOnly/openWorld annotations.

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?

Front-loaded with the action and source, then filters, then return shape — a sensible order with no wasted sentences. The parenthetical gloss on HRSA and the slightly long final sentence are minor padding.

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 fully: row composition, sort order, estimate flagging, and the richer detail-mode payload. Combined with zero required parameters and 100% schema coverage, an agent has everything needed to call it correctly on the first try.

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; the description earns above that by clarifying the mutually exclusive intent of `opportunity` (one record in full, with eligibility and all dates) and by framing the other filters as combinable narrowing options. It does not add syntax details beyond what the schema already provides for `open_on` or `limit`.

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 names a specific verb (search), a specific resource (HRSA funding opportunities listed on Grants.gov), and the exact scope (forecasts and posted notices). It also distinguishes two modes of the same tool — list rows vs. one opportunity in full when `opportunity` is supplied — so an agent knows precisely what it will get.

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 gives clear conditions for each filter path (text words, Health Center Program only, status, open-on-a-day) and explains that passing an opportunity number switches to a full single-record lookup. It stops short of naming alternatives or stating when not to use the tool, which keeps it below a 5.

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.