Skip to main content
Glama

code_crossref

Cross-reference a medical code across ICD-10, CPT, and HCPCS systems. Returns related codes grouped by system.

Instructions

Cross-reference a medical code across ICD-10, CPT, and HCPCS systems. Returns related codes grouped by system. Source: CodeReference DB (ICD-10/HCPCS: public domain).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesMedical code to cross-reference (e.g., "M79.3", "99213", "E0601")

Implementation Reference

  • src/tools.js:162-170 (registration)
    Tool definition/registration for 'code_crossref' in MCP_TOOLS array, defining name, description, price, REST endpoint ('/agent/v1/codes/crossref'), and Zod schema (requires 'code' string).
    {
      name: 'code_crossref',
      description: 'Cross-reference a medical code across ICD-10, CPT, and HCPCS systems. Returns related codes grouped by system. Source: CodeReference DB (ICD-10/HCPCS: public domain).',
      price: '$0.02',
      endpoint: '/agent/v1/codes/crossref',
      schema: {
        code: z.string().describe('Medical code to cross-reference (e.g., "M79.3", "99213", "E0601")'),
      },
    },
  • Zod input schema for 'code_crossref' — accepts a single required string parameter 'code' (medical code to cross-reference).
    schema: {
      code: z.string().describe('Medical code to cross-reference (e.g., "M79.3", "99213", "E0601")'),
    },
  • Generic handler that registers all MCP tools (including 'code_crossref') via s.tool(). Delegates execution by fetching the REST endpoint defined in the tool definition (POST /agent/v1/codes/crossref) with the provided params, returning JSON response or error.
    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 };
        }
      });
    }
  • Helper function that looks up a tool definition by name in the MCP_TOOLS array, used by the handler in index.js to find the endpoint and price for 'code_crossref'.
    export function getToolByName(name) {
      return MCP_TOOLS.find((t) => t.name === name);
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions the data source (public domain) but offers no details about response format, error handling, rate limits, or safety (e.g., read-only). This leaves the agent guessing about behavioral traits.

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 plus a source line, front-loaded with the core action and immediately informative. Every part earns its place without redundancy.

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 the tool's simplicity (one parameter, no output schema), the description covers the essential purpose and parameter context. It lacks output format details but provides enough for basic usage.

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 has 100% coverage for the single parameter 'code', and the description provides helpful examples (e.g., 'M79.3', '99213'). However, it adds limited extra meaning beyond the schema itself.

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's action: 'Cross-reference a medical code across ICD-10, CPT, and HCPCS systems' with a specific verb and resource, and it distinguishes from siblings like code_lookup and code_validate by emphasizing cross-system grouping.

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 usage for cross-system code comparison but lacks explicit guidance on when to use this tool versus siblings like code_lookup or code_validate. No alternatives or exclusions are mentioned.

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