Skip to main content
Glama

Find federal grant opportunities

find_grant_opportunities
Read-onlyIdempotent

Searches Grants.gov for open or forecasted federal grant opportunities by keyword, eligibility, agency, category, posting date and closing date. Returns up to 30 rows per page, per-item errors, and XLSX pipeline-tracker and ICS deadline downloads. Covers federal opportunities on Grants.gov only; private foundation, state and local grants are out of scope.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number after screening and sorting, e.g. 1; from 1 to 20.
keywordNoWords to search for, e.g. youth mentoring; quotes are removed.
agenciesNoDepartment or sub-agency codes, e.g. ["HHS", "DOC-EDA"].
statusesNoNotice status, e.g. ["posted"]; the default includes posted and forecasted notices.
categoriesNoFunding categories, e.g. ["ED", "HL"].
eligibilityNoApplicant types, e.g. ["nonprofit_501c3"]; unrestricted notices are included.
instrumentsNoFunding instruments, e.g. ["G"] for grants or ["CA"] for cooperative agreements.
max_resultsNoRows per page, e.g. 25; from 1 to 30.
closing_afterNoInclusive earliest closing date, e.g. 2026-10-21; the default is today in America/New_York.
closing_beforeNoInclusive latest closing date, e.g. 2026-12-20; at most 730 days after today.
match_all_wordsNotrue matches only notices containing every keyword word; false matches any word. Default false.
posted_within_daysNoNumber of days since posting, e.g. 7 for a weekly scan.
include_no_close_dateNotrue includes rolling or undated notices. Default true.

Output Schema

NameRequiredDescriptionDefault
pageYes
rowsYes
shownYes
errorsYes
sourceYes
matchedYes
summaryYes
has_nextYes
downloadsYes
attributionYes
retrieved_atYes
calendar_eventsYes
total_availableYes
deadline_time_noteYes
download_expires_atYes
deadline_time_includedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / closing_after / description
      Previous value: -"Inclusive earliest closing date, e.g. 2026-10-21; defaults to today in America/New_York."New value: +"Inclusive earliest closing date, e.g. 2026-10-21; the default is today in America/New_York."
    • changedInput schema / properties / include_no_close_date / description
      Previous value: -"Keep rolling or undated notices, e.g. true; default true."New value: +"true includes rolling or undated notices. Default true."
    • changedInput schema / properties / match_all_words / description
      Previous value: -"Require all keyword words, e.g. true; default false matches any word."New value: +"true matches only notices containing every keyword word; false matches any word. Default false."
    • changedInput schema / properties / statuses / description
      Previous value: -"Notice status, e.g. [\"posted\"]; defaults to posted and forecasted."New value: +"Notice status, e.g. [\"posted\"]; the default includes posted and forecasted notices."
    • addedOutput schema / properties / attribution
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / deadline_time_included
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / deadline_time_note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / download_expires_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / retrieved_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / rows / items / properties / close_estimated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / rows / items / properties / is_estimated
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / rows / items / required
      Previous value: -[
      -  "number",
      -  "title",
      -  "agency",
      -  "status",
      -  "posted",
      -  "close",
      -  "days_left",
      -  "ceiling",
      -  "floor",
      -  "link"
      -]New value: +[
      +  "number",
      +  "title",
      +  "agency",
      +  "status",
      +  "posted",
      +  "close",
      +  "close_estimated",
      +  "is_estimated",
      +  "days_left",
      +  "ceiling",
      +  "floor",
      +  "link"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "summary",
      -  "source",
      -  "matched",
      -  "shown",
      -  "total_available",
      -  "page",
      -  "has_next",
      -  "rows",
      -  "errors",
      -  "downloads",
      -  "calendar_events"
      -]New value: +[
      +  "summary",
      +  "source",
      +  "retrieved_at",
      +  "matched",
      +  "shown",
      +  "total_available",
      +  "page",
      +  "has_next",
      +  "rows",
      +  "errors",
      +  "downloads",
      +  "download_expires_at",
      +  "calendar_events",
      +  "attribution",
      +  "deadline_time_included",
      +  "deadline_time_note"
      +]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's marginal value is the pagination cap of 30 rows, per-item errors, and the XLSX/ICS download artifacts, which the agent could not infer from the schema. It does not explain how per-item errors are surfaced or whether downloads are always produced, leaving the behavioral picture partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding: capabilities first, then result shape, then scope limits. Every clause carries information an agent needs.

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 13 optional parameters, rich annotations and an output schema, the description covers source, result shape, pagination and scope adequately. It stops short of noting that all parameters are optional or that an unfiltered call returns everything, but the schema carries that.

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 every one of the 13 parameters already has documented semantics, defaults and examples. The description adds no per-parameter meaning beyond repeating the facet list (keyword, eligibility, agency, category, dates), which is the baseline case.

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?

States a specific verb and resource ("Searches Grants.gov for open or forecasted federal grant opportunities") and enumerates the filterable facets. The scope sentence makes it distinguishable from show_grant_details, which retrieves a single notice's detail rather than a filtered list.

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 an explicit boundary: federal Grants.gov notices only, with private foundation, state and local grants declared out of scope. It never names show_grant_details as the follow-up for full notice text, so the routing is implied rather than stated.

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