Skip to main content
Glama

Last day to appeal a denial

appeal_deadline
Read-onlyIdempotent

The last day to file an appeal of a Medicare, Medicare Advantage, Part D or commercial/ACA/employer plan denial, counted the way the rules count it (Medicare presumes receipt 5 days after the notice date), with days remaining, who decides, and the next level. Not legal advice; confirm the exact date with the official source it names.

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": {
      "program": "<program>",
      "noticeDate": "<noticeDate>"
    },
    "name": "appeal_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoAppeal level; 1 is the first appeal.
programYesoriginal_medicare, medicare_advantage, part_d, or commercial_aca.
receivedNotrue if noticeDate is the date the notice was actually received (skips Medicare's 5-day presumption).
noticeDateYesDate printed on the denial notice, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description goes further by disclosing the counting model (Medicare's 5-day receipt presumption) and what the result contains: days remaining, who decides, and the next level. It also carries the 'not legal advice' caveat, though it says nothing about how past-due or out-of-range cases are reported.

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 core computation and its counting rule are front-loaded in the first clause, with the output contents and the disclaimer trailing. It is dense but every clause - program scope, counting rule, return contents, caveat - carries information the agent needs.

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 usefully states what comes back and includes a legal disclaimer appropriate for a deadline tool. It is close to complete; only edge-case handling such as expired deadlines or the level-5 ceiling is unaddressed.

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 a baseline of 3 applies, but the description earns more by explaining the presumption mechanics that give the 'received' flag its meaning (true skips the 5-day presumption) and by enumerating the program families behind the enum. The 'level' parameter is left to 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?

The description names a specific resource and computation - the last day to file an appeal - and scopes it to named programs (Medicare, Medicare Advantage, Part D, commercial/ACA/employer). This is plainly distinguishable from the lookup-oriented siblings without opening any schema.

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

Usage Guidelines3/5

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

Usage is implied by the required inputs (a program and a printed notice date), and the closing sentence routes the agent to the official source for confirmation. There is no explicit statement of when not to use it or what to do for deadlines already elapsed or beyond level 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.

Resources