Skip to main content
Glama
mymedi-ai-mcp-server

mymedi-ai-mcp-server

by MyMedi-AI

Prior authorization status check

pa_status
Read-only

Check the status, dates, and expiration of a prior authorization request tracked in MyMedi-AI by PA ID or tracking number; it does not query payers or determine code requirements.

Instructions

Check the status of a prior authorization request tracked in your MyMedi-AI web workspace (by its MyMedi-AI PA id). Returns current status, dates, and expiration info. It does not query payers or say whether a code requires prior authorization, and returns not-found (refunded) if the PA was never entered in the web app.

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

Input Schema

NameRequiredDescriptionDefault
trackingNumberNoTracking number (alternative to authorizationId)
authorizationIdNoPrior authorization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.9
    • addedInput schema / properties / authorizationId / maxLength
      Added value: +500
    • addedInput schema / properties / trackingNumber / maxLength
      Added value: +500
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, non-open-world behavior, so the description's added value is the miss case: returns not-found/refunded when the PA was never entered in the web app, and the fact that no payer round-trip occurs. That is genuine behavioral context beyond the annotations, though the oddity of idempotentHint=false for a status read is left unaddressed.

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?

Three tight sentences, front-loaded with the core action, then return content, then exclusions and the miss case. No filler or restatement of the title.

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?

For a read-only lookup with no output schema, the description supplies the returned data shape (status, dates, expiration info) and the not-found behavior, which is what an agent needs to interpret results. Minor gap: it does not clarify which parameter wins if both id and tracking number are supplied.

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%, so both trackingNumber and authorizationId are documented in the schema itself; the description only mentions the PA-id path and never explains the tracking-number alternative or how the two relate. Baseline 3 is appropriate when the schema carries the parameter documentation.

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?

States a specific verb (check) and resource (prior authorization status) with an explicit scope qualifier: PAs tracked in the MyMedi-AI web workspace, addressed by MyMedi-AI PA id. It also names what it is not (no payer query, no PA-requirement determination), which separates it from pa_required_check and pa_predict without opening either schema.

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?

Clearly says when to use it (PA already entered in the web app) and gives explicit exclusions ('does not query payers or say whether a code requires prior authorization'), which routes the agent away from it toward the requirement-check tools. It never names the alternative sibling tools directly, so the routing is inferential rather than explicit.

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