Govcon Intel

Govcon Opportunity Scan

govcon_opportunity_scan

Read-onlyIdempotent

Search open government contracts and grants by keyword or agency. Returns matching opportunities, set-asides (e.g., 8(a), HUBZone, SDVOSB), deadline dates, and active SBIR solicitations. Needs no API key: the opportunity legs read a local snapshot of SAM.gov's public Contract Opportunities extract. Pass a free SAM.gov key as _apiKey only to reach postings newer than that snapshot.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-govcon-intel-api-key",
      "keywords": "cybersecurity",
      "set_aside": "8A"
    },
    "name": "govcon_opportunity_scan"
  }
}

Input Schema

Name	Required	Description
`_apiKey`	No	Optional — omit it. The opportunity legs answer keyless from the local snapshot of SAM.gov's public Contract Opportunities extract; a key is needed only to reach postings newer than that snapshot.
`keywords`	Yes	Search keywords (e.g., "cybersecurity", "AI machine learning", "cloud infrastructure")
`set_aside`	No	Set-aside type filter (e.g., "SBA", "8A", "HUBZone", "SDVOSB", "WOSB")

Output Schema

Name	Required	Description
`analysis`	Yes	Analysis type identifier
`keywords`	Yes	Search keywords used
`set_aside_filter`	Yes	Set-aside type filter applied or 'none'
`open_opportunities`	Yes	Open government opportunities matching keywords
`sbir_solicitations`	Yes	Active SBIR/STTR solicitations matching keywords
`recent_awards_in_space`	Yes	Recent federal awards in this market space
`set_aside_opportunities`	Yes	Set-aside specific opportunities (8(a), HUBZone, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 2, 2026

changedInput schema / properties / _apiKey / description

Previous value: -"SAM.gov API key — free at https://sam.gov. Required to retrieve open/set-aside opportunities; without it those legs return unavailable."New value: +"Optional — omit it. The opportunity legs answer keyless from the local snapshot of SAM.gov's public Contract Opportunities extract; a key is needed only to reach postings newer than that snapshot."

Changed1 schema field changedMay 28, 2026

changedInput schema / properties / _apiKey / description

Previous value: -"SAM.gov API key (optional)"New value: +"SAM.gov API key — free at https://sam.gov. Required to retrieve open/set-aside opportunities; without it those legs return unavailable."

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "analysis": {
+      "description": "Analysis type identifier",
+      "enum": [
+        "opportunity_scan"
+      ],
+      "type": "string"
+    },
+    "keywords": {
+      "description": "Search keywords used",
+      "type": "string"
+    },
+    "open_opportunities": {
+      "description": "Open government opportunities matching keywords",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "recent_awards_in_space": {
+      "description": "Recent federal awards in this market space",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "sbir_solicitations": {
+      "description": "Active SBIR/STTR solicitations matching keywords",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "set_aside_filter": {
+      "description": "Set-aside type filter applied or 'none'",
+      "type": "string"
+    },
+    "set_aside_opportunities": {
+      "description": "Set-aside specific opportunities (8(a), HUBZone, etc.)",
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "analysis",
+    "keywords",
+    "set_aside_filter",
+    "open_opportunities",
+    "set_aside_opportunities",
+    "recent_awards_in_space",
+    "sbir_solicitations"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-govcon-intel-api-key",
+    "keywords": "cybersecurity",
+    "set_aside": "8A"
+  },
+  {
+    "keywords": "AI machine learning cloud infrastructure"
+  }
+]

First observedApr 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive behavior; the description adds transparency about the snapshot data source and the conditional need for _apiKey. This goes beyond the annotations, although the phrase 'opportunity legs' is vaguely worded.

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?

The description is compact and front-loaded with the search purpose, followed by return contents and API-key note. It earns its sentences, though 'opportunity legs' introduces internal jargon that slightly reduces clarity.

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 a full output schema and informative annotations, the description does not need to explain return schemas. It covers the essential call requirements (keywords, optional set_aside, optional _apiKey) and the snapshot freshness nuance; the only notable gap is that 'by agency' is not operationalized by a parameter.

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 coverage is 100%, so the schema already documents keywords, set_aside, and _apiKey. The description repeats the _apiKey behavior and set-aside examples but does not add substantially new parameter meaning, and 'by agency' is unsupported by any schema property.

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?

The description uses a specific verb and resource: 'Search open government contracts and grants' against a 'local snapshot of SAM.gov's public Contract Opportunities extract', and enumerates returns (opportunities, set-asides, deadlines, SBIR solicitations). This differentiates it from siblings like govcon_agency_landscape and govcon_contractor_profile, though the phrase 'by keyword or agency' is not directly reflected in the input schema.

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?

It clearly frames when the tool is relevant (contract/grant search with optional set-aside filters) and gives operational guidance on API-key use for newer postings. However, it does not explicitly state when to prefer this over related govcon siblings or list exclusion criteria.

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

All Govcon Intel 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.

Resources

Need Help?