Skip to main content
Glama

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false; the description adds genuinely new context: list version and as-of date carried in the attested payload, a post-quantum signed settlement receipt, a verification URL, and a $1.00 USDC per-call cost. What it still omits is outcome behavior, such as what a hit versus a clear result looks like or how matching confidence is expressed.

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?

Front-loaded with the use case, then the mechanism, then provenance and price, which is a sensible order. Some attestation and verification phrasing is close to promotional, but it does convey real call behavior, so it is largely earned.

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?

There is no output schema, so the description should explain the shape of a screening result beyond the passing mention of list version and as-of date in the payload. For a compliance-decision tool, the absence of any description of hit/no-hit output or attestation fields leaves a meaningful gap.

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 0% with two unrequired parameters, so the description must carry the load, and it does name the two screening keys (provider name, NPI). It does not say whether at least one is mandatory, what name-matching semantics apply (exact vs fuzzy), or how the two inputs are combined when 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?

Names a specific verb and resource ("Screens HHS OIG LEIE") plus the matching keys (provider name or NPI), and frames the compliance use case. The explicit LEIE source distinguishes it from the SAM and OFAC screening siblings without needing to name 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?

Gives concrete trigger conditions: credentialing a healthcare provider or verifying vendor eligibility against federal exclusions. It does not state when NOT to use it, e.g. that other exclusion lists require the SAM or OFAC siblings, so the agent must infer list selection.

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