Skip to main content
Glama
Sign In

SpendQuery

by com.spendquery
OverviewDiscussionsAdmin

Find federal grant opportunities

grant_opportunities
Read-onlyIdempotent

Federal grant opportunities on Grants.gov: open ones soonest closing first (or forecast), by words and by who may apply, each with its number, agency, close date, award ceiling and estimated funding, and its spendquery.com page, plus up to 5 forecast grants on the same words (expected, not yet open). The search wants every word in the listing: with no match it tries fewer words and says what it searched for.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords in the grant's title or description, e.g. "homelessness" or "rural broadband".
whoNoWho may apply: nonprofit, local (cities and counties), state, tribe, university, small_business, business or individual.
stageNoopen (taking applications, soonest closing first) or forecast (expected).open

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?

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for adding real behavior: default result ordering, the fields carried per result, the automatic inclusion of up to 5 forecast grants even in open mode, and the fallback that relaxes to fewer words and reports what was searched. It stops short of stating result counts or pagination limits for the main list.

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 source are front-loaded, and every clause carries information about filters, ordering, or returned fields. The second and third sentences are dense run-ons that could be split for faster parsing.

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?

With no output schema, the description usefully enumerates the returned fields, and all three optional parameters are documented at full coverage. Remaining gaps are result-count limits and behavior with no filters at all, which are minor for a read-only search.

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 adds genuine meaning by explaining that the query matches all words in the listing (AND semantics), which the schema does not state. The who and stage semantics largely restate the enum descriptions.

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 resource and source (federal grant opportunities on Grants.gov) plus the core filters (words, eligibility), default ordering (soonest closing first), and the per-result fields returned. It is clearly distinguishable from siblings like search_local_bids, sbir_awards, or search_recipients.

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?

The stage behavior is spelled out (open = taking applications sorted by close date, forecast = expected), which implies when each mode applies. However, there is no explicit guidance on when to choose this tool over sibling search tools, nor any stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SpendQuery toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources