Skip to main content
Glama

Search US federal grant opportunities on Grants.gov

grants
Read-only

US federal grant opportunities from Grants.gov matching keywords: number, title, agency, open and close dates (YYYY-MM-DD), status and link, newest opening date first. Grants.gov matches keywords anywhere in the full listing, not only the title. Posted and forecasted opportunities by default. US government data. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesKeywords
limitNo1 to 25 (default 10)
statusNoposted, forecasted, closed or archived (optional)

Output Schema

NameRequiredDescriptionDefault
queryNo
totalNo
grantsNo
sourceNo
checkedAtNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Goes well past the readOnlyHint/openWorldHint annotations by disclosing two behaviors that materially affect invocation: a per-successful-call price of $0.002 paid via x402 across multiple chains, and that failed calls are not charged. Also states result ordering (newest opening date first) and the default status scope, which the annotations do not cover.

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 result shape and search scope are front-loaded, then defaults, then pricing — a sensible order with no repetition. 'US government data.' is a low-value sentence and the payment-network list is somewhat verbose, keeping it from a 5.

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 three-parameter, fully documented schema with an output schema available, the definition covers what an agent needs: scope of matching, default status filter, ordering, and cost model. Nothing critical is missing, though it never clarifies what happens when limit or status conflict with the defaults.

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 100%, so q, limit and status are already documented, including the 1-25 range and optional status values. The description adds one genuinely useful semantic — that q matches anywhere in the listing rather than title only, and that omitting status yields posted plus forecasted — but nothing about limit behavior or ordering interaction; baseline 3 applies.

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?

Names a specific verb and resource: searching US federal grant opportunities from Grants.gov by keyword, and enumerates the returned fields (number, title, agency, dates, status, link). An agent knows exactly what this tool retrieves and in what order, without opening the 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?

Gives clear operating context: keyword matching applies to the full listing not just titles, and results default to posted plus forecasted opportunities unless status is set. It does not name an alternative tool or state when not to use this one, so it stops short of 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.

Resources