Skip to main content
Glama

DenialPath

by io.github.maxbeech

Days left to file a claim for a payer

get_timely_filing
Read-onlyIdempotent

Days remaining to file an initial claim (or, if already past, how far over) for a payer given a date of service. daysRemaining and expired are null when we hold no published timely filing limit for that payer, which is common since many limits are contract-specific - check note before treating the result as an actual deadline. Free, no API key needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payerYesPayer slug, e.g. "aetna".
dateOfServiceYesISO yyyy-mm-dd, e.g. "2026-01-15".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / properties / dateOfService / description
      Previous value: -"ISO yyyy-mm-dd."New value: +"ISO yyyy-mm-dd, e.g. \"2026-01-15\"."
    • addedInput schema / properties / dateOfService / format
      Added value: +"date"
    • addedInput schema / properties / dateOfService / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / payer / enum
      Added value: +[
+  "medicare",
+  "medicaid",
+  "aetna",
+  "cigna",
+  "unitedhealthcare",
+  "anthem-bcbs",
+  "bcbs-general",
+  "humana",
+  "kaiser-permanente",
+  "tricare",
+  "molina",
+  "centene-ambetter",
+  "oscar-health",
+  "bright-health",
+  "wellcare",
+  "highmark",
+  "horizon-bcbs",
+  "independence-blue-cross",
+  "emblemhealth",
+  "health-net"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Read-only, idempotent, and non-destructive traits are already in annotations. The description adds behavioral context beyond that: the null behavior of "daysRemaining and expired" when no published limit exists, the contract-specific nature of limits, and the note about not treating results as actual deadlines. It also states the tool is free and requires no API key.

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?

The description is two sentences, front-loaded with the primary purpose, and every sentence earns its place. The first sentence states the exact function, the second provides critical caveats about null values and deadline validity. No fluff or repetition.

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?

Given no output schema, the description usefully explains the key output fields (daysRemaining, expired) and their null condition. It also covers the broader context that limits are often contract-specific. It doesn't list every possible field, but for this simple tool the description provides sufficient completeness.

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?

The input schema already provides 100% coverage with clear descriptions for both parameters (payer enum with example, date of service format example). The description does not add parameter-specific semantics beyond the phrase "given a date of service," which aligns with the schema. Baseline 3 is appropriate.

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 clearly states what the tool does: it returns "days remaining to file an initial claim" for a specific payer and date of service. It also distinguishes from siblings by focusing on timely filing limits, which is a distinct resource from claim checks, appeals, denials, MUE, or NCCI edits.

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 description implies when to use the tool: when you need the days left to file a claim for a payer given a service date. It also includes a caveat to "check note before treating the result as an actual deadline," which guides interpretation. No explicit alternatives are named, but the context is clear.

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

All DenialPath toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct function: claim checking, appeal drafting, denial explanation, MUE lookup, NCCI edits lookup, and timely filing. There is no overlap in purpose, and the descriptions make the boundaries clear.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (check_claim, draft_appeal, explain_denial, get_mue, get_ncci_edits, get_timely_filing). The verbs are specific and the nouns are meaningful, creating a predictable and readable naming scheme.

Tool Count5/5

Six tools is well within the ideal range for a focused server. The count feels appropriate for the denial management domain, with each tool earning its place and no redundancy.

Completeness5/5

The toolset covers the full denial lifecycle: pre-claim checking (check_claim), denial explanation (explain_denial), appeal drafting (draft_appeal), and supporting lookups (get_mue, get_ncci_edits, get_timely_filing). No obvious gaps exist for the stated purpose.

Resources