Skip to main content
Glama

Medicare Revalidation Due Date Sentinel

Revalidation Deadline Sentinel: revalidation lookup

revalidation_lookup
Read-onlyIdempotent

Use this when you need to know when a US healthcare provider must revalidate its Medicare enrollment (PECOS). For 1 to 50 NPI numbers: each Medicare enrollment (Part A, DME, Non-DME Part B) with its revalidation due date read from the official CMS Revalidation Due Date List, days left, status (upcoming, date_passed, not_set) and list version. No names returned. Not a consumer report under the FCRA. Not affiliated with or endorsed by CMS or any U.S. government agency. Price: 0.01 USDC per call (x402). Free trial: set free_trial to true (3 calls per day per caller).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "npi": "<npi>"
    },
    "name": "revalidation_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYes1 to 50 NPI numbers (10 digits, valid check digit), comma-separated
free_trialNoSet to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.

Output Schema

NameRequiredDescriptionDefault
dataNoData source, license and the only fields read
noteNoHow to read not_set, no extensions, when to file
rulesNoRules applied, with official URL and status
licenceNoLicence of the source data: nom, url, source
resultsNoOne entry per NPI: npi, found, enrollments (enrollment_id: organizations only, null for an individual practitioner's enrollment; state, enrollment_type {code, label: Part A, DME, Non-DME Part B}, provider_type, specialty, revalidation_due_date, adjusted_due_date, due_date (the earlier date), later_due_date, status (upcoming, date_passed, not_set), days_left, as_of, time_zone)
disclaimerNoNot legal advice; not affiliated with CMS; not a consumer report
list_versionNoVersion of the CMS list read, e.g. 2026-11-01
official_toolNoCMS lookup tool, the authoritative record

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / free_trial
      Added value: +{
      +  "description": "Set to true to ask for the free trial (3 calls per day per caller, shared with the web route, within a daily cap for the service). Without it, the tool asks for an x402 payment.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the bar is low, yet the description adds a lot: output fields (due date, days left, status values upcoming/date_passed/not_set, list version), data provenance (official CMS Revalidation Due Date List), a per-call price under x402, and free-trial mechanics including the 3-calls-per-day cap. These are behavioral facts an agent could not infer from annotations.

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 capability, output shape, and cost are front-loaded in the first sentences, with legal disclaimers trailing. The FCRA and non-affiliation sentences are boilerplate but plausibly required for this data domain; the whole block is dense but not padded with redundancy.

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 an output schema present, return values need not be spelled out, yet the description summarizes them usefully; pricing and trial limits are covered. It does not address failure behavior for invalid NPIs or rate limits beyond the free-trial cap, leaving a small gap for a paid lookup tool.

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 the schema already documents both the npi pattern (1-50 ten-digit NPIs) and free_trial. The description restates the 1-50 NPI range and the free-trial semantics without adding format or validation detail beyond the schema, matching the 3 baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: determining when a US healthcare provider's Medicare enrollment (PECOS) must be revalidated, including Part A/DME/Non-DME Part B. It also states scope limits ('No names returned') that sharpen the boundary. It does not explicitly differentiate from the sibling revalidation_example, which keeps it from a 5.

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 this when you need to know when a US healthcare provider must revalidate' gives a clear triggering condition, and the no-names/FCRA statements imply when-not to use it. No alternative tool is named and no explicit exclusions are given, so it stops short of a 5.

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.