Skip to main content
Glama
grants-discovery-mcp-server

grants-discovery-mcp-server

Get Grant Opportunity Details

grants_get_opportunity
Read-onlyIdempotent

Retrieve complete Grants.gov opportunity details by numeric ID, including eligibility, award amounts, key dates, and agency contacts; use search first to find the ID.

Instructions

Get the full announcement for one Grants.gov opportunity: summary, eligibility, award ceiling/floor, total funding, expected number of awards, cost sharing, key dates, and agency contact.

Use grants_search_opportunities first to find the numeric opportunity ID.

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": {
      "opportunity_id": "<opportunity_id>"
    },
    "name": "grants_get_opportunity"
  }
}

Input Schema

NameRequiredDescriptionDefault
opportunity_idYesNumeric opportunity ID from search results, e.g. 359145
response_formatNo'markdown' for readable text, 'json' for structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile needs no restating. The description adds genuine context by disclosing the breadth of the returned record and the dependency on a prior search for the ID, though it says nothing about behavior for invalid/missing IDs or rate limits.

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 waste, with the capability statement front-loaded and the prerequisite search step placed after it. Every clause earns its place by describing either output scope or the calling sequence.

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?

No output schema exists, but the description compensates by enumerating the returned fields so the agent can judge fitness of the result. Only minor gaps remain, such as error behavior or record-size expectations for a full announcement payload.

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%, with opportunity_id documented (numeric, example 359145) and response_format enum explained, so the schema carries the semantics. The description only reinforces that the ID is numeric and must come from search results, adding provenance but little beyond the structured fields.

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 (get) and resource (full announcement for one Grants.gov opportunity) and then enumerates the concrete payload: summary, eligibility, award ceiling/floor, total funding, expected awards, cost sharing, key dates, agency contact. This distinguishes it clearly from the sibling search tools that return lists rather than full details.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use grants_search_opportunities first to find the numeric opportunity ID,' naming the alternative and the precondition that selects it. An agent knows both when to use this tool and what must happen before calling it.

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