Skip to main content
Glama

BRAINIAC Public Infrastructure Lookups

Search open Grants.gov opportunities

public-infrastructure_grants-gov-opportunity-search
Read-onlyIdempotent

Search open US federal grant synopses and forecasts from the Grants.gov daily extract. Price $0.03 USDC. POST /api/v1/public-infrastructure/grants-gov-opportunity-search. An unpaid call returns the x402 payment terms and does not run.

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": "public-infrastructure_grants-gov-opportunity-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cfdaNocfda, string, length 1 to 20. Optional.
kindNokind, array. Optional.
limitNolimit, integer, from 1 to 100. Required.
queryNoquery, string, length 1 to 200. Optional.
agencyCodeNoagencyCode, string, length 1 to 40. Optional.
closingBeforeNoclosingBefore, string. Optional.
opportunityNumberNoopportunityNumber, string, length 1 to 50. Optional.
eligibleApplicantsNoeligibleApplicants, array. Optional.

Output Schema

NameRequiredDescriptionDefault
countNocount. Number.
sourcesNosources. Array.
extractDateNoextractDate. String.
limitationsNolimitations. Array.
opportunitiesNoopportunities. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, yet the description adds substantive context they cannot convey: the $0.03 USDC price, the exact POST endpoint, and critically that an unpaid call returns x402 payment terms without executing. That last point prevents a failed invocation and is exactly the kind of disclosure this dimension rewards.

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?

Three short sentences, front-loaded with what the tool searches, then cost, then endpoint and payment failure mode. No filler, though the repeated endpoint path is slightly redundant with the tool name.

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?

Output schema exists so return values need not be explained, and the payment model is well covered. However, the schema labels 'limit', 'kind' and 'eligibleApplicants' items as 'Required' while zero parameters are actually required, and the description does not clarify this or describe matching behavior, pagination, or 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 description coverage is 100%, so the schema already documents all eight parameters, and the description adds no per-parameter meaning, format hints, or defaults. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource with scope: 'Search open US federal grant synopses and forecasts from the Grants.gov daily extract.' An agent knows exactly what corpus is being queried. It does not name distinguishing alternatives, but the sibling tools are unrelated public-data lookups, so misrouting risk is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb 'Search' and the phrase 'open ... synopses and forecasts' – there is no explicit statement of when to prefer this tool or when not to use it. No preconditions or exclusions are given beyond the payment note.

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