SAM.gov Opportunities MCP server

get_opportunity

Read-onlyIdempotent

Retrieve a SAM.gov opportunity by notice ID, URL, or solicitation number; a solicitation number returns all related notices, including amendments and award details.

Instructions

Get one SAM.gov opportunity by notice ID, URL or solicitation number. A solicitation number returns all of its notices (for example the solicitation, its amendments and the award notice with the winner and amount).

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": {
      "id": "<id>"
    },
    "name": "get_opportunity"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	A SAM.gov notice ID (32 hex chars), a sam.gov/opp/... URL, or a solicitation number such as FA813226Q0061.
`detail`	No	'full' adds the description, all contacts and attachment links.	full

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the safety profile is free. The description earns credit on top by disclosing a non-obvious return behavior: a solicitation number expands to multiple notices including amendments and the award notice with winner and amount.

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, no filler, and the identifier forms are front-loaded. The second sentence is spent entirely on the one behavior an agent could not infer.

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 rich annotations, a full schema and an output schema present, the description carries only the burden of explaining the multi-notice expansion, which it does. Minor gaps, such as behavior when an id matches nothing, are not covered but are also not essential for calling it correctly.

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 both the id formats and the compact/full detail switch are already fully documented. The description restates the id formats but adds nothing about the detail parameter, so it does not exceed the schema baseline.

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 and resource ('Get one SAM.gov opportunity') and immediately names the three accepted identifier forms. The word 'one' plus the identifier-based lookup makes it distinguishable from search_opportunities, which is a query tool.

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 identifier-based framing ('by notice ID, URL or solicitation number') makes the when-to-use situation clear: you already have a reference, not a keyword. It never explicitly says to use search_opportunities when you lack an identifier, so it stops short of full alternative routing.

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

Deploy Server