Skip to main content
Glama

Oig Cia Obligations

oig_cia_obligations
Read-onlyIdempotent

What obligations does this entity's Corporate Integrity Agreement actually impose, Board Resolution, Independent Review Organization (IRO) reviews, Compliance Officer/Committee, Annual/Implementation reporting, a disclosure program, excluded-persons screening? Resolves the entity (same matching as oig_cia_check) or takes a direct document_url (from oig_cia_check's agreement_url field), fetches the agreement PDF LIVE from oig.hhs.gov, extracts its text, and reports which of those obligation categories appear in the text with a short excerpt for each. Not every CIA includes every category, a sole-individual CIA typically has no Board Resolution clause, and some older closed agreements have no PDF posted at all (reported as found:false, not an error). 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": "SNAP Diagnostics"
    },
    "name": "oig_cia_obligations"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCompany or individual name to look up (resolved the same way as oig_cia_check). Omit if passing document_url directly.
document_urlNoA specific agreement PDF URL under oig.hhs.gov/documents/cias/..., e.g. from a prior oig_cia_check call's agreement_url field. Overrides name-based lookup when given.

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 useful context beyond that: the PDF is fetched live from oig.hhs.gov, text is extracted, and each found category comes with a short excerpt. It does not discuss rate limits or failure modes beyond the found:false note, so a 3 is appropriate.

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 leading question front-loads the tool's purpose effectively, and the remaining sentences cover mechanism, caveats, and provenance. It is somewhat dense in a single paragraph but every clause carries information, 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 two-parameter, no-output-schema tool, the description covers resolution, fetching, extraction, reporting shape, and the found:false edge case, which is what an agent needs to call it correctly. Minor gaps around response size or excerpt length remain, but overall it is complete.

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 both parameters are already documented, including that document_url overrides name. The description reinforces the linkage by naming agreement_url as the source of document_url, but adds little syntax or format detail beyond the schema. Baseline 3 holds.

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 (extracts/reports obligations) and resource (the entity's Corporate Integrity Agreement) and enumerates the exact obligation categories it looks for. It also distinguishes itself from the sibling oig_cia_check, so an agent can tell the two apart 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 Guidelines4/5

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

Explains the two entry paths clearly: resolve by name the same way oig_cia_check does, or pass a document_url taken from oig_cia_check's agreement_url field, which effectively tells the agent to chain from the check tool. It also sets expectations (not every CIA has every category, sole-individual CIAs lack Board Resolution, older agreements may have no PDF). It stops short of an explicit 'use this instead of oig_cia_check when...' contrast.

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.