Skip to main content
Glama

map_icd10_to_icd11

Read-onlyIdempotent

Search ICD-10 codes in the ICD-11 index to find matching entities by title, definition, or synonym. Use for exploratory lookups, not as authoritative mapping.

Instructions

This tool runs the ICD-10 code as a query string against the ICD-11 search index. The search matches the code against ICD-11 entity titles, definitions, and synonyms; it does not consult any curated ICD-10 → ICD-11 mapping. Results are search hits, not authoritative mappings.

For authoritative ICD-10 → ICD-11 mappings (clinical coding, billing, migration projects), consult the WHO transition tables at https://icd.who.int/browse11/Downloads/Download.

Use this tool for exploratory lookups: confirming a code exists in ICD-11 text, finding ICD-11 entities whose descriptions reference an ICD-10 code, or seeding a manual mapping review. Do not present the results as ICD-10 → ICD-11 equivalents to clinical or billing consumers.

Provide a code like "E11" (Type 2 diabetes) or "I21" (Acute MI).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icd10_codeYesICD-10 code to query in the ICD-11 search index (e.g., E11, I21.0, J18.9)

Implementation Reference

  • The main handler function for map_icd10_to_icd11. Parses the icd10_code param, searches via WHO client, and returns formatted text results (search hits, not authoritative mappings).
    async function handleMapICD10ToICD11(args: Record<string, unknown>): Promise<CallToolResult> {
      try {
        const params = MapICD10ToICD11ParamsSchema.parse(args);
        const client = getWHOClient();
        const code = params.icd10_code.toUpperCase().trim();
    
        const response = await client.search(code, 'en', 10);
        const results = response.destinationEntities || [];
    
        const lines: string[] = [];
        lines.push(`# ICD-11 search results for ICD-10 code "${code}"`);
        lines.push('');
        lines.push(
          `This output is a text search of the ICD-11 catalog using "${code}" as the query string. The hits below are ICD-11 entities whose titles, definitions, or synonyms contain that string. They are not curated ICD-10 → ICD-11 mappings. For authoritative mappings, use the WHO transition tables: https://icd.who.int/browse11/Downloads/Download.`,
        );
        lines.push('');
    
        if (results.length === 0) {
          lines.push('## No search hits');
          lines.push('');
          lines.push('Nothing in the ICD-11 catalog matched this code as a text query.');
          lines.push('');
          lines.push('**Next steps:**');
          lines.push('- Try `icd11_search` with the condition name instead of the ICD-10 code');
          lines.push('- The concept may have been restructured between revisions');
          lines.push('- Consult the WHO transition tables linked above');
        } else {
          lines.push(`## Search hits (${Math.min(results.length, 10)} shown)`);
          lines.push('');
          lines.push('| ICD-11 Code | Title |');
          lines.push('|-------------|-------|');
    
          for (const result of results.slice(0, 10)) {
            const code11 = result.theCode || 'N/A';
            const title = result.title || 'N/A';
            lines.push(`| ${code11} | ${title} |`);
          }
    
          lines.push('');
          lines.push(
            'These are search candidates intended for manual review. To assign an ICD-11 code for clinical coding or billing, verify each candidate against the WHO transition tables linked above.',
          );
        }
    
        return {
          content: [{ type: 'text', text: lines.join('\n') }],
        };
      } catch (error) {
        return handleToolError(error);
      }
    }
  • Zod schema for map_icd10_to_icd11 parameters: requires a non-empty string icd10_code field.
    export const MapICD10ToICD11ParamsSchema = z.object({
      icd10_code: z
        .string()
        .min(1)
        .describe('ICD-10 code to query in the ICD-11 search index (e.g., E11, I21.0, J18.9)'),
    });
  • Registration of the mapICD10ToICD11Tool with its handler via toolRegistry.register().
    toolRegistry.register(mapICD10ToICD11Tool, handleMapICD10ToICD11);
  • Tool definition (Tool object) with name, description, inputSchema, and annotations for the MCP SDK.
    const mapICD10ToICD11Tool: Tool = {
      name: 'map_icd10_to_icd11',
      description: `This tool runs the ICD-10 code as a query string against the ICD-11 search index. The search matches the code against ICD-11 entity titles, definitions, and synonyms; it does not consult any curated ICD-10 → ICD-11 mapping. Results are search hits, not authoritative mappings.
    
    For authoritative ICD-10 → ICD-11 mappings (clinical coding, billing, migration projects), consult the WHO transition tables at https://icd.who.int/browse11/Downloads/Download.
    
    Use this tool for exploratory lookups: confirming a code exists in ICD-11 text, finding ICD-11 entities whose descriptions reference an ICD-10 code, or seeding a manual mapping review. Do not present the results as ICD-10 → ICD-11 equivalents to clinical or billing consumers.
    
    Provide a code like "E11" (Type 2 diabetes) or "I21" (Acute MI).`,
      inputSchema: buildInputSchema(MapICD10ToICD11ParamsSchema),
      annotations: READ_ONLY_TOOL_ANNOTATIONS,
    };
  • Prompt instruction referencing map_icd10_to_icd11 as a text-search heuristic, surfaced to the LLM when cross-mapping comes up.
      'If no terminology returns a confident match, say so explicitly rather than guessing. Note: `map_icd10_to_icd11` is currently a text-search heuristic, not an authoritative mapping — surface this caveat if cross-mapping comes up.',
    ].join('\n');
Behavior5/5

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

Annotations indicate read-only, idempotent, open-world. Description adds behavioral details: searches titles/definitions/synonyms, does not consult curated mapping, results are search hits. No contradiction with annotations.

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 paragraphs: mechanism, authoritative alternative, usage guidance + example. Front-loaded with action verb 'runs'. No wasted words; each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with one parameter, annotations covering safety, and no output schema, the description thoroughly covers purpose, limitations, and usage context. Explains what results are (search hits) and what they are not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter icd10_code with schema description already providing examples. The tool description reinforces with new examples and adds context (e.g., 'Type 2 diabetes'), slightly improving clarity. With 100% schema coverage, baseline is 3, but the added semantic examples justify a 4.

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 runs an ICD-10 code as a query against the ICD-11 search index to find search hits, not authoritative mappings. It distinguishes from potential siblings like find_equivalent by specifying it does not consult any curated mapping. Examples (E11, I21) reinforce the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use: exploratory lookups, confirming code existence, finding references, seeding manual mapping. States when not to use: not for authoritative mapping or clinical coding/billing. Provides alternative resource: WHO transition tables.

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/SidneyBissoli/medical-terminologies-mcp'

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