Skip to main content
Glama

Sam Search Exclusions

sam_search_exclusions
Read-onlyIdempotent

Search the SAM.gov Exclusions list, parties DEBARRED, suspended, or otherwise excluded from receiving federal contracts, grants, or assistance. Answers "is this company/person barred from federal contracting" for KYB / vendor-vetting / procurement due diligence. Filter by name, US state, and classification (Firm / Individual / Vessel / Special Entity). Returns each excluded party with the exclusion type, program, excluding agency, and active/termination dates. Distinct from OFAC sanctions (see sanctions_screen), this is the federal procurement debarment list.

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": {
      "name": "Smith",
      "limit": 2
    },
    "name": "sam_search_exclusions"
  }
}

Input Schema

NameRequiredDescriptionDefault
ueiNoOptional, check one specific UEI against the debarment list. More reliable than a name for KYB, since names collide and are transcribed inconsistently.
nameNoName to search (company or individual), e.g. "Smith Construction". Matched against the excluded party name; an exact UEI also matches. Optional if you pass `uei` instead, supply one of the two.
limitNoNumber of results (1-100, default 10).
stateNoOptional 2-letter US state to filter by, e.g. "VA".
offsetNoRows to skip for paging (default 0).
_apiKeyNoOptional, omit it. This search answers keyless from the local snapshot of SAM.gov's public Exclusions extract, which is refreshed daily.
classificationNoOptional classification: "Firm", "Individual", "Vessel", or "Special Entity Designation".
include_terminatedNoAccepted, but it currently changes NOTHING, SAM.gov's daily Exclusions extract carries only exclusions in force, so there are no terminated records for it to add. Measured 2026-09-13 over 400 sampled rows across four names with the filter explicitly disabled: zero carried a termination date in the past. Read an empty result as "not debarred TODAY", never as "never debarred", a bar that has since ended is absent from this source entirely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 Exclusions extract, which is refreshed daily."New value: +"Optional, omit it. This search answers keyless from the local snapshot of SAM.gov's public Exclusions extract, which is refreshed daily."
    • changedInput schema / properties / include_terminated / description
      Previous value: -"Accepted, but it currently changes NOTHING — SAM.gov's daily Exclusions extract carries only exclusions in force, so there are no terminated records for it to add. Measured 2026-09-13 over 400 sampled rows across four names with the filter explicitly disabled: zero carried a termination date in the past. Read an empty result as \"not debarred TODAY\", never as \"never debarred\" — a bar that has since ended is absent from this source entirely."New value: +"Accepted, but it currently changes NOTHING, SAM.gov's daily Exclusions extract carries only exclusions in force, so there are no terminated records for it to add. Measured 2026-09-13 over 400 sampled rows across four names with the filter explicitly disabled: zero carried a termination date in the past. Read an empty result as \"not debarred TODAY\", never as \"never debarred\", a bar that has since ended is absent from this source entirely."
    • changedInput schema / properties / name / description
      Previous value: -"Name to search (company or individual), e.g. \"Smith Construction\". Matched against the excluded party name; an exact UEI also matches. Optional if you pass `uei` instead — supply one of the two."New value: +"Name to search (company or individual), e.g. \"Smith Construction\". Matched against the excluded party name; an exact UEI also matches. Optional if you pass `uei` instead, supply one of the two."
    • changedInput schema / properties / uei / description
      Previous value: -"Optional — check one specific UEI against the debarment list. More reliable than a name for KYB, since names collide and are transcribed inconsistently."New value: +"Optional, check one specific UEI against the debarment list. More reliable than a name for KYB, since names collide and are transcribed inconsistently."
  2. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "limit": 2,
      -    "name": "Smith"
      -  },
      -  {
      -    "name": "Smith Construction",
      -    "state": "VA"
      -  },
      -  {
      -    "classification": "Individual",
      -    "limit": 5,
      -    "name": "John Doe"
      -  }
      -]New value: +[
      +  {
      +    "limit": 2,
      +    "name": "Smith"
      +  },
      +  {
      +    "uei": "NZJHL7G6CZV5"
      +  },
      +  {
      +    "classification": "Firm",
      +    "limit": 20,
      +    "name": "Construction"
      +  },
      +  {
      +    "limit": 2,
      +    "name": "Smith",
      +    "state": "TX"
      +  }
      +]
    • changedInput schema / properties / include_terminated / description
      Previous value: -"Include exclusions that have already been terminated (default false — only exclusions in force are returned). A terminated exclusion is a historical fact, not a current bar."New value: +"Accepted, but it currently changes NOTHING — SAM.gov's daily Exclusions extract carries only exclusions in force, so there are no terminated records for it to add. Measured 2026-09-13 over 400 sampled rows across four names with the filter explicitly disabled: zero carried a termination date in the past. Read an empty result as \"not debarred TODAY\", never as \"never debarred\" — a bar that has since ended is absent from this source entirely."
    • changedInput schema / properties / name / description
      Previous value: -"Name to search (company or individual), e.g. \"Smith Construction\". Matched against the excluded party name; an exact UEI also matches."New value: +"Name to search (company or individual), e.g. \"Smith Construction\". Matched against the excluded party name; an exact UEI also matches. Optional if you pass `uei` instead — supply one of the two."
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[]
  3. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "_apiKey": "your-samgov-api-key",
      -    "name": "Smith Construction",
      -    "state": "VA"
      -  },
      -  {
      -    "_apiKey": "your-samgov-api-key",
      -    "classification": "Individual",
      -    "limit": 5,
      -    "name": "John Doe"
      -  }
      -]New value: +[
      +  {
      +    "limit": 2,
      +    "name": "Smith"
      +  },
      +  {
      +    "name": "Smith Construction",
      +    "state": "VA"
      +  },
      +  {
      +    "classification": "Individual",
      +    "limit": 5,
      +    "name": "John Doe"
      +  }
      +]
  4. Changed6 schema fields changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"SAM.gov API key — required. Free at https://sam.gov/content/entity-information; a key on an account with a SAM.gov role allows 1,000 requests/day."New value: +"Optional — omit it. This search answers keyless from the local snapshot of SAM.gov's public Exclusions extract, which is refreshed daily."
    • addedInput schema / properties / include_terminated
      Added value: +{
      +  "description": "Include exclusions that have already been terminated (default false — only exclusions in force are returned). A terminated exclusion is a historical fact, not a current bar.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Name to search (company or individual), e.g. \"Smith Construction\". Matched against the exclusion name."New value: +"Name to search (company or individual), e.g. \"Smith Construction\". Matched against the excluded party name; an exact UEI also matches."
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip for paging (default 0).",
      +  "type": "number"
      +}
    • addedInput schema / properties / uei
      Added value: +{
      +  "description": "Optional — check one specific UEI against the debarment list. More reliable than a name for KYB, since names collide and are transcribed inconsistently.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "_apiKey"
      -]New value: +[
      +  "name"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"SAM.gov API key"New value: +"SAM.gov API key — required. Free at https://sam.gov/content/entity-information; a key on an account with a SAM.gov role allows 1,000 requests/day."
  6. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-samgov-api-key",
      +    "name": "Smith Construction",
      +    "state": "VA"
      +  },
      +  {
      +    "_apiKey": "your-samgov-api-key",
      +    "classification": "Individual",
      +    "limit": 5,
      +    "name": "John Doe"
      +  }
      +]
  7. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds substantial context beyond that: it answers keyless from a daily-refreshed local snapshot, and it warns that include_terminated changes nothing and that an empty result means 'not debarred today,' never 'never debarred' — a critical interpretation caveat an agent could not infer from structured fields.

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?

Front-loads the core purpose, then the use-case question, then filters, then return shape, then sibling differentiation. Dense but every sentence carries information; nothing is redundant with the schema.

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?

No output schema exists, yet the description states what each result carries (exclusion type, program, excluding agency, active/termination dates). Combined with the empty-result interpretation caveat and the keyless/snapshot note, an agent has everything needed to call and interpret this tool.

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 every parameter including uei, name, state, classification, and include_terminated is already documented in the schema, and the description adds no syntax or format detail beyond it. Baseline 3 is appropriate when the schema does the heavy lifting; the description's value here is framing, not parameter semantics.

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 (search the SAM.gov Exclusions list) and immediately defines the population: parties debarred, suspended, or excluded from federal contracts, grants, or assistance. It explicitly distinguishes itself from OFAC sanctions and names the sibling sanctions_screen, so an agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases (KYB, vendor-vetting, procurement due diligence) and frames the question it answers: 'is this company/person barred from federal contracting.' It also names the alternative (sanctions_screen) and the condition that separates them, federal procurement debarment vs. OFAC sanctions.

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.