Skip to main content
Glama

Search Opportunities

search_opportunities
Read-onlyIdempotent

Search Grants.gov for currently-open or recently-closed federal funding opportunities. Filter by keyword, opportunity status, agency code, funding category, or date range. Returns opportunity number, title, agency, open/close dates, and assistance listing numbers (formerly CFDA).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alnNoAssistance Listing Number / CFDA number (e.g., "10.001")
limitNoRows per page (1-1000, default 25)
offsetNo0-based start record (default 0)
statusNoforecasted | posted | closed | archived (default posted; use a pipe to combine, e.g. "posted|forecasted")
keywordNoFull-text query
agenciesNoComma-separated agency codes (e.g., "EPA,USDA,NIH")
funding_categoriesNoComma-separated category codes (e.g., "ED" education, "ENV" environment, "ST" science)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of opportunities matching search criteria
returnedYesNumber of opportunities returned in this response
opportunitiesYesList of opportunity search results

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "agencies": "EPA,NOAA",
      +    "funding_categories": "ENV",
      +    "keyword": "climate resilience",
      +    "limit": 25,
      +    "status": "posted"
      +  },
      +  {
      +    "aln": "47.041",
      +    "keyword": "research",
      +    "limit": 50,
      +    "offset": 0,
      +    "status": "posted|forecasted"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "opportunities": {
      +      "description": "List of opportunity search results",
      +      "items": {
      +        "properties": {
      +          "agency": {
      +            "description": "Agency name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "agency_code": {
      +            "description": "Agency code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "assistance_listing_numbers": {
      +            "description": "Assistance listing numbers (formerly CFDA)",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "close_date": {
      +            "description": "Opportunity close date",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "doc_type": {
      +            "description": "Document type",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "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"
      +            ]
      +          },
      +          "open_date": {
      +            "description": "Opportunity open date",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "status": {
      +            "description": "Opportunity status",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "description": "Opportunity title",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "returned": {
      +      "description": "Number of opportunities returned in this response",
      +      "type": "number"
      +    },
      +    "total": {
      +      "description": "Total number of opportunities matching search criteria",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "returned",
      +    "opportunities"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations (readOnlyHint, idempotentHint, destructiveHint, openWorldHint) already provide a strong safety profile. The description adds context about searching federal funding opportunities and return fields, but this does not go significantly beyond the annotations.

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?

The description is two sentences, front-loaded with the main action, and contains no fluff. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, rich annotations, and 7 parameters with full schema descriptions, the description is complete. It covers purpose, filters, and return fields adequately.

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%, meaning each parameter has a description in the schema. The description provides a brief summary of filterable fields but does not add meaning beyond the schema's per-parameter 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?

The description clearly states the tool searches Grants.gov for federal funding opportunities, specifies the scope (currently-open or recently-closed), lists filterable fields, and mentions return fields. This distinguishes it from siblings like get_opportunity.

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?

The description implies usage for broad searches with various filters but does not explicitly state when to use this tool versus alternatives or provide exclusions. It is clear but lacks explicit guidance.

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.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx/ask_pipeworx_grounded/deep_research all handle broad queries; multiple Polymarket tools exist for edge finding; entity_profile/compare_entities/recent_changes/resolve_entity overlap on company data. An agent would struggle to pick the right tool.

Naming Consistency2/5

Naming patterns are mixed: some use verb_noun (search_opportunities, get_opportunity), some are phrases (ask_pipeworx_grounded, polymarket_edge_tracker), and some are vague (recall, forget). No consistent convention across the set.

Tool Count2/5

32 tools is high, but the core issue is that the server name 'Grants Gov' implies a narrow focus, yet only 2 tools are about grants. The sheer number of unrelated tools makes the set feel bloated and unfocused.

Completeness3/5

For the actual domain of general data querying and prediction markets, the tool surface is fairly complete, covering many sources. However, for 'Grants Gov' it is severely incomplete (missing all but opportunities). Overall, the scope is broad but lacks depth in any one area.