Skip to main content
Glama
Goingparabolic

painprep-mcp-server

Generate Prior Authorization Letter

get_prior_auth_letter
Read-only

Generate a payer-ready prior-authorization letter for a procedure by merging patient details, CPT codes, ICD-10, and necessity rationale; leaves unspecified fields as fill-in blanks.

Instructions

Generates a formal, payer-ready prior-authorization / medical-necessity letter for a procedure, merging supplied patient and clinical details with the procedure’s CPT codes, recommended primary ICD-10 code, evidence grade, and necessity rationale. Any field left unspecified is rendered as a clearly-marked fill-in blank. The structured medical-necessity worksheet is appended when available. PREMIUM tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icd10NoPrimary ICD-10 code; defaults to the recommended primary code.
payerNoPayer / insurance company name.
memberIdNoInsurance member / Medicare beneficiary ID.
diagnosisNoPrimary diagnosis narrative (e.g. "left L5 radiculopathy").
painScoreNoPain score, e.g. "7/10 at rest, 9/10 with activity".
procedureYesProcedure name, id, or CPT code.
patientDOBNoPatient date of birth.
patientNameNoPatient full name.
providerNPINoOrdering provider NPI.
providerNameNoOrdering provider name and credentials.
imagingFindingsNoRelevant MRI/CT/X-ray findings with date.
symptomDurationNoSymptom duration, e.g. "5 months".
conservativeCareNoFailed conservative care with durations, e.g. "8 weeks PT, NSAIDs x6 weeks".
includeWorksheetNoAppend the structured medical-necessity worksheet template (default true).
functionalLimitationsNoFunctional limitations narrative.
Behavior1/5

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

The description claims the tool 'generates' a letter, which is a write operation, but annotations declare readOnlyHint=true. This is a direct contradiction. The description does not clarify side effects, idempotency, or other behavioral traits beyond the fill-in blank note.

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 a single focused paragraph with no unnecessary words. It front-loads the primary action and adds key behavioral notes concisely.

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?

For a tool with 15 parameters and no output schema, the description covers the generation process and behavior of unspecified fields, but lacks details on return format, synchronization, or limitations. The mention of 'PREMIUM tier' hints at access constraints but is not fleshed out.

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 coverage is 100% with detailed parameter descriptions. The description adds general context (merging details, fill-in blanks, worksheet) but does not enhance understanding of individual parameters beyond what the schema already provides.

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 it generates a prior-authorization/medical-necessity letter, specifying it is payer-ready and merges supplied details with CPT codes, ICD-10, etc. This unambiguously distinguishes it from sibling tools that retrieve codes or checklists.

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?

The description implies use when a formal letter is needed, but does not explicitly state when to use this tool versus alternatives like get_cpt_codes or get_icd10_codes. No when-not or exclusion guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Goingparabolic/painprep-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server