Skip to main content
Glama

Medicare Revalidation Due Date Sentinel

Revalidation Deadline Sentinel: free sample

revalidation_example
Read-onlyIdempotent

Free sample: a real answer for one hospital NPI, same shape as revalidation_lookup.

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": "revalidation_example"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that the result is a "real answer" mirroring the sibling's shape, which is useful context, but it does not disclose which NPI is used, whether the data is live or cached, or any limits on sample usage.

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?

A single short sentence with the differentiator ("free sample") front-loaded and no filler. It is efficient, though brevity comes at the cost of the missing specifics noted above.

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?

An output schema exists, so the return shape need not be explained, and the description correctly points at revalidation_lookup for parity. What remains unexplained is how a parameterless tool resolves "one hospital NPI" and what the sample's limitations are, which an agent needs before calling it.

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?

With zero parameters, the baseline would normally be a 4, but the description asserts an answer "for one hospital NPI" while the schema exposes no NPI input. That mismatch leaves the agent unclear on how the NPI is selected, which is a meaningful semantic gap rather than a strength.

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

Purpose3/5

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

"Free sample: a real answer for one hospital NPI" implies a preview of revalidation deadline data, but the description never states the actual verb or resource (e.g. "looks up the revalidation deadline"). The distinguishing factor versus revalidation_lookup is present ("free sample"), yet the core purpose is only inferable from the title and the sibling name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The word "sample" hints at trial/preview usage, but there is no explicit statement of when to call this instead of revalidation_lookup, no note that it returns a fixed or limited record, and no guidance on what to do after sampling. The agent must guess the selection rule.

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.