Skip to main content
Glama

Oig Cia Check

oig_cia_check
Read-onlyIdempotent

Does this healthcare company or individual have an HHS-OIG Corporate Integrity Agreement (CIA)? Checks a name against the current HHS-OIG CIA roster, companies and individuals OIG agreed not to exclude from Medicare/Medicaid in exchange for binding compliance obligations, as part of a False Claims Act or other settlement. Different from an EXCLUSION (see the leie / ny-omig-exclusions packs): a CIA entity is still participating, under obligations. An exact name match is the strongest signal; a normalized-name or partial/token match is returned as a labelled CANDIDATE, since CIA entity names are often compound (a company plus named co-signers), e.g. searching "SNAP Diagnostics" finds "SNAP Diagnostics, LLC and Gil Raviv" as a candidate. Returns, for the best match: status (Effective/Suspended/Closed/Refused), effective date, term/duration, settlement amount, and the agreement PDF URL (fetched live from the entity's own detail page, not stale). Returns found:false with the list's as-of date and total agreement count when no match exists. Sourced from HHS-OIG, keyless.

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": "Alliance Parent, Inc."
    },
    "name": "oig_cia_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCompany or individual name to check, e.g. "SNAP Diagnostics" or "Alliance Parent, Inc.". Any word order; partial names are matched as candidates.
limitNoMaximum candidates to return (default 5, max 20). Only the top/best candidate is enriched with live detail-page data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: candidates are labelled, detail is fetched live from the entity's own page rather than stale, and found:false comes back with an as-of date and total count. Those additions are solid but modest, keeping this at a 3 rather than higher.

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-loads the core question before definitions and caveats, and every sentence carries information about matching behavior, return values, or sourcing. It is dense but not padded, though the single long paragraph could be broken up for scanability.

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 no output schema, the description does the work of explaining return fields (status, effective date, term, settlement amount, PDF URL) and the no-match shape with as-of date. This is nearly complete for a name-check tool; only explicit sibling routing is missing.

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 100% and both parameters are already documented, so the schema does the heavy lifting. The description adds a modest amount of matching semantics, explaining why compound entity names surface as candidates (the "SNAP Diagnostics" example), which is not fully spelled out in the schema.

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?

Opens with a specific question-form verb and a precise resource (HHS-OIG Corporate Integrity Agreement roster), then explicitly contrasts itself with EXCLUSION data and names the leie / ny-omig-exclusions packs. An agent can immediately tell this apart from an exclusion lookup or the sibling oig_cia_list.

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 clear when-to-use context by contrasting CIA status with exclusion status, and explains that partial matches return labelled CANDIDATE results. It does not explicitly say when to prefer oig_cia_list or oig_cia_obligations over this tool, so it stops short of full alternative routing.

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.