Skip to main content
Glama

Sam Set Aside Opportunities

sam_set_aside_opportunities
Read-onlyIdempotent

Find federal contract opportunities reserved for a specific class of small business, total or partial small business, 8(a), women-owned (WOSB/EDWOSB), HUBZone, service-disabled veteran-owned (SDVOSB), veteran-owned, Indian small business economic enterprise and Buy Indian. Answers "what HUBZone contracts are open", "recent 8(a) set-asides", "women-owned small business opportunities in NAICS 541512". Reads SAM.gov's public daily Contract Opportunities extract, so it costs no API key and works on the plain code (SBA, HZC, SDVOSBC, 8A, WOSB) or on the ordinary phrasing ("HUBZone", "women-owned", "8(a)", "service-disabled veteran"). Returns titles, solicitation numbers, deadlines, agencies and NAICS, with a mirror field reporting how fresh the snapshot is.

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": {
      "limit": 25,
      "keyword": "construction",
      "set_aside": "SDVOSB"
    },
    "name": "sam_set_aside_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (1-100, default 10)
naicsNoOptional NAICS code filter
_apiKeyNoOptional, omit it. This search answers 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.
keywordNoOptional keyword to narrow results
set_asideYesSet-aside type (required). Either the SAM.gov code, SBA (total small business), SBP (partial), 8A, 8AN (8(a) sole source), WOSB, EDWOSB, HZC (HUBZone), HZS (HUBZone sole source), SDVOSBC, SDVOSBS, VSA (veteran-owned), ISBEE, IEE, BICiv, or the ordinary phrasing ("small business", "HUBZone", "women-owned", "8(a)", "service-disabled veteran"), which is resolved to the code for you.

Output Schema

NameRequiredDescriptionDefault
limitYesNumber of results returned in this request
opportunitiesYes
total_recordsYesTotal number of matching set-aside opportunities
set_aside_typeYesSet-aside type being searched

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — omit it. This search answers 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."New value: +"Optional, omit it. This search answers 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."
    • changedInput schema / properties / set_aside / description
      Previous value: -"Set-aside type (required). Either the SAM.gov code — SBA (total small business), SBP (partial), 8A, 8AN (8(a) sole source), WOSB, EDWOSB, HZC (HUBZone), HZS (HUBZone sole source), SDVOSBC, SDVOSBS, VSA (veteran-owned), ISBEE, IEE, BICiv — or the ordinary phrasing (\"small business\", \"HUBZone\", \"women-owned\", \"8(a)\", \"service-disabled veteran\"), which is resolved to the code for you."New value: +"Set-aside type (required). Either the SAM.gov code, SBA (total small business), SBP (partial), 8A, 8AN (8(a) sole source), WOSB, EDWOSB, HZC (HUBZone), HZS (HUBZone sole source), SDVOSBC, SDVOSBS, VSA (veteran-owned), ISBEE, IEE, BICiv, or the ordinary phrasing (\"small business\", \"HUBZone\", \"women-owned\", \"8(a)\", \"service-disabled veteran\"), which is resolved to the code for you."
  2. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "_apiKey": "your-samgov-api-key",
      -    "keyword": "construction",
      -    "limit": 25,
      -    "set_aside": "SDVOSB"
      -  },
      -  {
      -    "_apiKey": "your-samgov-api-key",
      -    "set_aside": "HUBZone"
      -  }
      -]New value: +[
      +  {
      +    "keyword": "construction",
      +    "limit": 25,
      +    "set_aside": "SDVOSB"
      +  },
      +  {
      +    "set_aside": "HUBZone"
      +  }
      +]
    • changedInput schema / properties / _apiKey / description
      Previous value: -"SAM.gov API key"New value: +"Optional — omit it. This search answers 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."
    • changedInput schema / required
      Previous value: -[
      -  "set_aside",
      -  "_apiKey"
      -]New value: +[
      +  "set_aside"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / set_aside / description
      Previous value: -"Set-aside type (required): SBA (Small Business), SDVOSB (Service-Disabled Veteran), HUBZone, 8AN (8(a)), WOSB (Women-Owned), EDWOSB (Economically Disadvantaged Women-Owned)"New value: +"Set-aside type (required). Either the SAM.gov code — SBA (total small business), SBP (partial), 8A, 8AN (8(a) sole source), WOSB, EDWOSB, HZC (HUBZone), HZS (HUBZone sole source), SDVOSBC, SDVOSBS, VSA (veteran-owned), ISBEE, IEE, BICiv — or the ordinary phrasing (\"small business\", \"HUBZone\", \"women-owned\", \"8(a)\", \"service-disabled veteran\"), which is resolved to the code for you."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "limit": {
      +      "description": "Number of results returned in this request",
      +      "type": "number"
      +    },
      +    "opportunities": {
      +      "items": {
      +        "properties": {
      +          "active": {
      +            "description": "Active status indicator",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "classification_code": {
      +            "description": "Classification code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "department": {
      +            "description": "Procuring department/agency",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "naics_code": {
      +            "description": "Primary NAICS code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "office": {
      +            "description": "Procuring office name",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "posted_date": {
      +            "description": "Date opportunity was posted",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "response_deadline": {
      +            "description": "Proposal response deadline",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "set_aside": {
      +            "description": "Small business set-aside type",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "solicitation_number": {
      +            "description": "Unique solicitation identifier",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "sub_tier": {
      +            "description": "Sub-tier agency code",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "description": "Opportunity title",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "type": {
      +            "description": "Procurement type",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "ui_link": {
      +            "description": "URL to opportunity details on SAM.gov",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "set_aside_type": {
      +      "description": "Set-aside type being searched",
      +      "type": "string"
      +    },
      +    "total_records": {
      +      "description": "Total number of matching set-aside opportunities",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "set_aside_type",
      +    "total_records",
      +    "limit",
      +    "opportunities"
      +  ],
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-samgov-api-key",
      +    "keyword": "construction",
      +    "limit": 25,
      +    "set_aside": "SDVOSB"
      +  },
      +  {
      +    "_apiKey": "your-samgov-api-key",
      +    "set_aside": "HUBZone"
      +  }
      +]
  6. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, but the description adds material behavior beyond them: the data source is SAM.gov's public daily Contract Opportunities extract, no API key is required, and the `mirror` field signals snapshot staleness. Those are exactly the cost and freshness facts an agent needs before calling.

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?

It is a single front-loaded paragraph that states purpose, data source, accepted inputs and outputs in that order, which reads well. The enumerated code/phrase list and example questions are somewhat long-winded but each contributes usable detail rather than filler.

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 an output schema present, the return-field listing is optional; the description still covers the source, keyless operation, freshness caveat and accepted input vocabulary, which is complete for a filtered search tool. The remaining gap is routing guidance versus the general sam_search_opportunities sibling.

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%, and the schema already documents `set_aside` codes and the ordinary-phrasing resolution, so the description's restatement of codes and phrasings adds little new meaning. The NAICS example query is a modest addition; baseline 3 is appropriate when the schema carries the parameter semantics.

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 opens with a specific verb and resource ('Find federal contract opportunities reserved for a specific class of small business') and enumerates the set-aside classes covered, so the resource is unmistakable. It never names the sibling tool sam_search_opportunities, so an agent must infer for itself why one would pick this over the general opportunity search.

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 quoted example questions ('what HUBZone contracts are open', 'recent 8(a) set-asides', 'women-owned small business opportunities in NAICS 541512') give concrete usage contexts an agent can pattern-match against. There is no explicit when-not-to-use guidance or pointer to sam_search_opportunities / sam_get_opportunity for non-set-aside or single-posting lookups.

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.