Skip to main content
Glama
Gov Tenders & Grants MCP

Gov Tenders & Grants MCP

Grants.gov Search API: federal grants list with deadlines

publicrecords--grants-gov-scraper
Read-only

Search open US federal grants on Grants.gov by keyword, agency, status, and deadline; returns opportunity details, eligibility, and official source links.

Instructions

Grants.gov Search API: federal grants list with deadlines. Which federal grants are open right now? Searches Grants.gov and returns opportunity, agency, deadline, eligibility and the source link.

When to use: Use when you need open US federal grant opportunities from Grants.gov with agency, deadline and eligibility.

Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset.

Behavior: starts one run of the Apify Actor "publicrecords/grants-gov-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/publicrecords/grants-gov-scraper

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": "publicrecords--grants-gov-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
agencyNoMapped to API body agencies (e.g. HHS, EPA, NSF).
statusNoMapped to API oppStatuses. Use forecasted|posted|closed|archived or pipe-joined.forecasted|posted
keywordNoSearch keyword (e.g. education, cybersecurity). Leave empty for all.
maxItemsNoCap on opportunity rows (deduped by opportunityId).
openDateToNoClient-side filter on openDate. Inclusive.
closeDateToNoClient-side filter on closeDate. Inclusive.
fetchDetailsNoHydrate synopsis via fetchOpportunity.
openDateFromNoClient-side filter on openDate. Accepts MM/DD/YYYY or YYYY-MM-DD. Inclusive.
closeDateFromNoClient-side filter on closeDate. Inclusive. Useful for 'still open' windows.
postedWithinDaysNoServer-side filter mapped to search2 dateRange (posted-date lookback). Verified values: 3,7,14,21,28,35,42,49,56,90,180,365. Omit for no posted-date filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, but the description adds genuinely non-obvious behavior: a run of the Apify Actor is started via the hosted MCP gateway, it uses the caller's own APIFY_TOKEN and Apify account, and the response includes run/dataset IDs for paging. It does not mention credit/cost implications of starting a run, which is the main remaining gap.

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?

Labeled sections (When to use / Returns / Behavior / Docs) are front-loaded and easy to scan. The opening restates the title and adds a rhetorical question ('Which federal grants are open right now?') that duplicates the purpose line, minor waste but not harmful.

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 10-parameter, no-required-input search tool with no output schema, the description covers purpose, return shape (one row per result plus run/dataset IDs), auth requirements and read-only nature. Only cost/credit behavior of the underlying Actor run is left unexplained.

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 10 parameters is already documented in the schema, including the pipe-joined status format and the verified postedWithinDays values. The description adds no parameter-level meaning beyond naming agency, deadline and eligibility as returned fields.

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 ('Searches Grants.gov and returns opportunity, agency, deadline, eligibility') with a clear geographic/source scope (US federal grants via Grants.gov). That scope implicitly separates it from the EU TED, UK tender and USAspending siblings, though no sibling is named explicitly.

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?

An explicit 'When to use' line gives the condition: needing open US federal grant opportunities with agency, deadline and eligibility. It gives no negative guidance or named alternative (e.g. use the govcon feed for non-Grants.gov sources), so it stops short of a 5.

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