Skip to main content
Glama

pa_status

Check the status of a prior authorization request: returns current status, dates, and expiration info using authorization ID or tracking number.

Instructions

Check the status of a prior authorization request. Returns current status, dates, and expiration info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorizationIdNoPrior authorization ID
trackingNumberNoTracking number (alternative to authorizationId)

Implementation Reference

  • Tool definition and schema for 'pa_status'. Defines the tool's name, description, price, endpoint, and Zod schema with optional 'authorizationId' and 'trackingNumber' parameters.
    {
      name: 'pa_status',
      description: 'Check the status of a prior authorization request. Returns current status, dates, and expiration info.',
      price: '$0.02',
      endpoint: '/agent/v1/pa/status',
      schema: {
        authorizationId: z.string().optional().describe('Prior authorization ID'),
        trackingNumber: z.string().optional().describe('Tracking number (alternative to authorizationId)'),
      },
    },
  • src/index.js:19-61 (registration)
    Generic tool registration in the MCP server. The 'pa_status' tool is registered via the loop over MCP_TOOLS; its handler makes a POST request to '/agent/v1/pa/status' with the provided parameters.
    for (const tool of MCP_TOOLS) {
      s.tool(tool.name, tool.description, tool.schema, async (params) => {
        const toolDef = getToolByName(tool.name);
        if (!toolDef) {
          return { content: [{ type: 'text', text: `Unknown tool: ${tool.name}` }], isError: true };
        }
        try {
          const response = await fetch(`${API_BASE_URL}${toolDef.endpoint}`, {
            method: 'POST',
            headers: {
              'Content-Type': 'application/json',
              ...(API_KEY && { 'X-API-Key': API_KEY }),
              'X-Agent-ID': 'mcp-client',
              'User-Agent': '@mymedi-ai/mcp-server/1.2.1',
            },
            body: JSON.stringify(params),
          });
          if (response.status === 402) {
            const paymentInfo = await response.json();
            return {
              content: [{ type: 'text', text: JSON.stringify({
                error: 'payment_required',
                message: `This tool costs ${toolDef.price} per call. Register at ${API_BASE_URL}/bot-marketplace/register for an API key with 10 free starter credits, or pay per call with on-chain USDC (no signup) via the x402 protocol.`,
                price: toolDef.price, register: `${API_BASE_URL}/bot-marketplace/register`, ...paymentInfo,
              }, null, 2) }], isError: true,
            };
          }
          if (!response.ok) {
            const error = await response.json().catch(() => ({ message: response.statusText }));
            return { content: [{ type: 'text', text: JSON.stringify({ error: true, status: response.status, ...error }, null, 2) }], isError: true };
          }
          const data = await response.json();
          const creditsSpent = response.headers.get('X-Credits-Spent');
          const creditsRemaining = response.headers.get('X-Credits-Remaining');
          if (creditsSpent) {
            data._billing = { creditsSpent: parseInt(creditsSpent, 10), creditsRemaining: creditsRemaining ? parseInt(creditsRemaining, 10) : undefined, priceUSD: toolDef.price };
          }
          return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
        } catch (err) {
          return { content: [{ type: 'text', text: JSON.stringify({ error: true, message: err.message, hint: 'Ensure MCP_API_BASE_URL and MCP_API_KEY environment variables are set.' }, null, 2) }], isError: true };
        }
      });
    }
  • src/index.js:68-71 (registration)
    Sandbox/scanning registration for 'pa_status'. Returns 'sandbox' text without making real API calls, used for tool discovery without credentials.
    for (const tool of MCP_TOOLS) {
      sandboxServer.tool(tool.name, tool.description, tool.schema,
        async () => ({ content: [{ type: 'text', text: 'sandbox' }] }));
    }
  • Helper function to look up a tool definition by name. Used by the handler to retrieve endpoint and price info for 'pa_status'.
    export function getToolByName(name) {
      return MCP_TOOLS.find((t) => t.name === name);
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool 'returns current status, dates, and expiration info,' which implies a safe, read-only operation. However, it does not mention any authentication requirements, rate limits, or data freshness, leaving some behavioral aspects unclear.

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 sentence of 12 words, efficiently conveying the purpose and return details. It is front-loaded and contains no superfluous information.

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?

Given no output schema, the description partially explains return values (status, dates, expiration). However, it does not specify that at least one of the two optional parameters is required or describe error handling. For a simple lookup, it is minimally sufficient but lacks full context.

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 description coverage is 100% (both parameters have descriptions). The description adds that it returns status, dates, and expiration info, but does not add new meaning beyond what the schema provides for the parameters. Baseline 3 applies.

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 the tool checks the status of a prior authorization request and specifies the return values (status, dates, expiration info). It distinguishes itself from sibling tools like claims_validate by focusing specifically on prior authorization status.

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 does not explicitly provide when-to-use or when-not-to-use guidance, nor does it mention alternatives. The purpose is implied by the name and description, but no exclusion criteria or context for selection among sibling tools is given.

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/MyMedi-AI/mymedi-ai-mcp-server'

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