Grants Gov

Get Opportunity

get_opportunity

Read-onlyIdempotent

Fetch full details for a Grants.gov opportunity by ID. Returns synopsis text, eligibility, award ceiling/floor, attachments, contact info, and version history.

Input Schema

Name	Required	Description	Default
`opportunity_id`	Yes	Numeric opportunity ID (returned by search_opportunities as "id")

Output Schema

Name	Required	Description
`id`	Yes	Numeric opportunity ID
`cfdas`	Yes	CFDA/Assistance Listing Numbers
`title`	Yes	Opportunity title
`agency`	Yes	Agency name
`number`	Yes	Opportunity number
`synopsis`	Yes	Full synopsis description text
`agency_code`	Yes	Agency code
`attachments`	Yes	Opportunity attachments and documents
`award_floor`	Yes	Minimum award amount
`eligibility`	Yes	Eligibility requirements
`archive_date`	Yes	Archive date
`contact_name`	Yes	Agency contact person name
`posting_date`	Yes	Date opportunity was posted
`award_ceiling`	Yes	Maximum award amount
`contact_email`	Yes	Agency contact email address
`contact_phone`	Yes	Agency contact phone number
`response_date`	Yes	Response submission date
`grants_gov_url`	Yes	Direct link to opportunity on Grants.gov
`applicant_types`	Yes	List of eligible applicant types
`expected_awards`	Yes	Expected number of awards
`closing_date_desc`	Yes	Closing date description
`estimated_funding`	Yes	Estimated total funding available
`funding_categories`	Yes	List of funding activity categories
`funding_instruments`	Yes	List of funding instrument types

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "opportunity_id": 381934
-  }
-]New value: +[
+  {
+    "opportunity_id": 360869
+  }
+]

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "opportunity_id": 381934
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "agency": {
+      "description": "Agency name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "agency_code": {
+      "description": "Agency code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "applicant_types": {
+      "description": "List of eligible applicant types",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "archive_date": {
+      "description": "Archive date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "attachments": {
+      "description": "Opportunity attachments and documents",
+      "items": {
+        "properties": {
+          "download_url": {
+            "description": "URL to download attachment",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "file_name": {
+            "description": "Attachment file name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "folder": {
+            "description": "Attachment folder name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "award_ceiling": {
+      "description": "Maximum award amount",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "award_floor": {
+      "description": "Minimum award amount",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "cfdas": {
+      "description": "CFDA/Assistance Listing Numbers",
+      "items": {
+        "properties": {
+          "number": {
+            "description": "CFDA number",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Program title",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "closing_date_desc": {
+      "description": "Closing date description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "contact_email": {
+      "description": "Agency contact email address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "contact_name": {
+      "description": "Agency contact person name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "contact_phone": {
+      "description": "Agency contact phone number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "eligibility": {
+      "description": "Eligibility requirements",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "estimated_funding": {
+      "description": "Estimated total funding available",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "expected_awards": {
+      "description": "Expected number of awards",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "funding_categories": {
+      "description": "List of funding activity categories",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "funding_instruments": {
+      "description": "List of funding instrument types",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "grants_gov_url": {
+      "description": "Direct link to opportunity on Grants.gov",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Numeric opportunity ID",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "number": {
+      "description": "Opportunity number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "posting_date": {
+      "description": "Date opportunity was posted",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "response_date": {
+      "description": "Response submission date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "synopsis": {
+      "description": "Full synopsis description text",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Opportunity title",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "number",
+    "title",
+    "agency_code",
+    "agency",
+    "synopsis",
+    "eligibility",
+    "award_ceiling",
+    "award_floor",
+    "estimated_funding",
+    "expected_awards",
+    "funding_instruments",
+    "funding_categories",
+    "applicant_types",
+    "cfdas",
+    "posting_date",
+    "response_date",
+    "closing_date_desc",
+    "archive_date",
+    "contact_name",
+    "contact_email",
+    "contact_phone",
+    "attachments",
+    "grants_gov_url"
+  ],
+  "type": "object"
+}

First observedMay 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds useful scope context by naming the data it surfaces (synopsis, eligibility, award ceiling/floor, attachments, contact, version history), but says nothing about behavior on an unknown or stale ID, rate limits, or truncation.

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?

Two tight sentences with the operation front-loaded and the payload described second. The enumerated return list mildly duplicates the output schema, but it is brief enough to earn its place as a scannable signal of value.

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?

An output schema exists, so return values need not be spelled out in detail, and annotations cover the safety semantics; the description fills in the domain content of the response. It is nearly complete for a simple by-ID fetch, missing only sibling differentiation and failure-mode behavior.

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?

With 100% schema description coverage on a single parameter, the schema fully documents opportunity_id as a numeric ID sourced from search_opportunities. The description contributes nothing further about the parameter, which is acceptable given the coverage baseline.

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 ('Fetch full details for a Grants.gov opportunity by ID') and enumerates the returned content, so the agent knows exactly what the call yields. It does not, however, distinguish itself from the nearby get_historical_opportunity sibling, which an agent retrieving an ID could easily confuse with it.

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 ID' signals this is the lookup to run once you already hold an opportunity ID, but no sentence names when to use it versus search_opportunities or get_historical_opportunity. The tie to search_opportunities ('returned by search_opportunities as "id"') lives in the schema, not the description.

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

All Grants Gov tools Inspect

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.