Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cms_revoked_providers

Read-only

Search CMS's public revoked Medicare providers list to check if a provider or supplier has been barred from re-enrollment, with reason and effective date.

Instructions

Search CMS's PUBLIC 'Revoked Medicare Providers & Suppliers' list — the legally-published register of Medicare enrollment revocations, with the revoked provider's identity, provider type, revocation reason, effective date, and re-enrollment-bar expiration (CMS 'Revoked Providers and Suppliers', keyless; data.cms.gov data-API, ~7,059 rows). A vetting lane in the same class as OFAC / SAM-exclusions lists. Input (ALL optional — the ~7K-row list is safe to page unfiltered): npi (10-digit), state (2-letter, EXACT), lastName (→ LAST_NAME, exact), size (1–100, default 25), offset. Returns { revocations:[{ enrollmentId, npi, name, state, providerType, revocationReason, revocationEffectiveDate, reenrollmentBarExpiration }] } + honest _meta (which notes this is CMS's public revocation list — a due-diligence signal, NOT a current-eligibility, guilt, or fitness determination). ★HONESTY: totalAvailable is the EXACT count from a SEPARATE stats sub-query (found_rows), NEVER the returned-rows length (null + note if count fails). name coalesces ORG_NAME else FIRST_NAME + LAST_NAME; NPI/reasons/dates null-never-empty. Genuine no-match → honest empty; 4xx → invalid_input/not_found; 5xx → THROWS; 200 non-array/non-JSON → schema_drift. KEYLESS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npiNoAn optional 10-digit National Provider Identifier (→ NPI), e.g. '1003000126'. Validated ^\d{10}$.
sizeNoMax revocation rows to return (1–100, default 25). Offset-paginated.
stateNoAn optional 2-letter US state/territory code (→ STATE_CD, EXACT match), e.g. 'FL', 'CA'. Validated ^[A-Za-z]{2}$.
offsetNoRow offset for pagination (default 0). Page with _meta.pagination.nextOffset.
lastNameNoAn optional last-name filter (→ LAST_NAME, EXACT match). Allowed: letters/digits/space/. , ' - (≤100 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description richly discloses behavior: totalAvailable comes from a separate stats sub-query and never the returned-rows length, name coalesces ORG_NAME over FIRST_NAME+LAST_NAME, NPI/reasons/dates are null-never-empty, no-match returns an honest empty result, 4xx/5xx/200-non-array cases are mapped, and the tool is keyless. This goes far beyond annotation coverage.

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?

Although dense, the description is well-structured and front-loaded: purpose, source, parameter semantics, return shape, honesty guarantees, and error behavior each earn their place. No filler is present, and the detail is justified by the absence of an output schema and the need to convey non-obvious pagination and null-handling behavior.

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

Completeness5/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 fully compensates by specifying the exact returned fields, the _meta behavior, error handling conventions, paging semantics, and data source. An agent has everything needed to select and invoke the tool correctly without consulting external documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all five parameters, but the description adds operational meaning: all inputs are optional, the small row count makes unfiltered paging safe, state and lastName are exact matches, and offset pagination is tied to _meta.pagination.nextOffset. This adds actionable guidance beyond bare schema descriptions.

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 opens with the specific verb 'Search' and names the exact resource: CMS's public 'Revoked Medicare Providers & Suppliers' list. It further distinguishes the tool from adjacent vetting sources by calling it 'a vetting lane in the same class as OFAC / SAM-exclusions lists' and clarifying it is CMS's public revocation register.

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?

It provides clear use context: this is for CMS revocation vetting, is keyless, and is safe to page unfiltered because the full list is only ~7,059 rows. It also sets a boundary by stating it is 'NOT a current-eligibility, guilt, or fitness determination,' which helps agents avoid overinterpreting results, though it stops short of explicitly naming when to choose it over specific sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools