Skip to main content
Glama

Stratalize Intelligence

Get Oig Exclusion Screening

get_oig_exclusion_screening
Read-only

Use when credentialing a healthcare provider or verifying vendor eligibility against federal exclusions. Screens HHS OIG LEIE by provider name or NPI with list version and as-of date in the attested payload. Source: HHS OIG LEIE synced exclusions. 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_oig_exclusion_screening"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNo
provider_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing the attested-payload contents (list version and as-of date), the post-quantum signed settlement receipt, an independent verify URL, and a $1.00 USDC per-call cost. Cost and verifiability are exactly the operational facts an agent cannot get from annotations or schema.

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 triggering condition is front-loaded in the first clause, and the four sentences each carry distinct information (when, what data, provenance, cost). The attestation/verification sentences edge toward promotional framing, but they convey a real operational fact, so little is wasted.

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?

For a simple read-only lookup with two parameters and no output schema, the definition covers source, use case, provenance, verification and price. The remaining gap is the response shape (match/no-match semantics) and the at-least-one-identifier requirement, neither of which is stated.

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?

With 0% schema description coverage the description must carry the parameter burden. It names the two lookup modes ('by provider name or NPI'), which is useful, but it never states that at least one identifier is required given zero required parameters, nor does it describe expected identifier formatting or what happens if both are supplied.

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?

The description names a specific verb and dataset: 'Screens HHS OIG LEIE by provider name or NPI.' Naming the exact federal source (LEIE) alongside the credentialing/vendor-eligibility framing lets an agent distinguish this from SAM or OFAC screening siblings without opening a schema.

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 opening 'Use when credentialing a healthcare provider or verifying vendor eligibility against federal exclusions' gives a clear triggering context. It stops short of explicit routing, e.g. it never tells the agent when to prefer get_sam_exclusion_screening or get_ofac_sanctions_screening instead, so no exclusion guidance is present.

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