Skip to main content
Glama

get_sam_exclusion_screening

Read-only

Use when verifying federal contractor or grantee eligibility against SAM.gov exclusions. Queries SAM Exclusions API by entity name, UEI, or CAGE with conservative name matching and live attestation metadata. Source: SAM.gov Exclusions API. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $1.00 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sam_exclusion_screening"
  }
}

Input Schema

NameRequiredDescriptionDefault
ueiNo
cage_codeNo
entity_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, open-world, so safety is covered. The description adds genuinely non-obvious behavior: conservative name matching, live attestation metadata, a signed settlement receipt with a verification URL, and a $1.00 USDC per-call cost — cost and attestation are material facts not in any structured field. It still omits what a negative/no-match result looks like.

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?

Roughly four short sentences: trigger, mechanism, provenance, attestation and price. The trigger is front-loaded and every sentence carries distinct operational or commercial information; nothing is redundant.

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

Completeness3/5

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

With no output schema, the description should convey what comes back; it only gestures at 'live attestation metadata' and an exclusion match, without stating result shape, match confidence, or how to read a no-hit. For a paid screening tool this is an incomplete picture of the response.

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 0%, so the description is doing the work: it names all three identifiers (entity name, UEI, CAGE) and flags 'conservative name matching' as the name-path behavior. However, it never states that the required array is empty (at least one identifier must be supplied), nor any precedence between identifiers or format expectations for UEI/CAGE, leaving a real ambiguity for a 0-required 3-param tool.

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 gives a specific verb and resource ('Queries SAM Exclusions API by entity name, UEI, or CAGE') and a concrete decision context (verifying federal contractor/grantee eligibility). The explicit SAM.gov source implicitly separates it from the OIG and OFAC screening siblings, though it never names them.

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?

'Use when verifying federal contractor or grantee eligibility against SAM.gov exclusions' is a clear triggering condition. There is no when-not guidance or explicit pointer to the OIG/OFAC siblings for other screening regimes, so the agent must infer that this is the SAM-specific path.

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.

Resources