Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

convert_icd_mesh

Read-onlyIdempotent

Map ICD-9-CM or ICD-10-CM codes to MeSH terms and vice versa to standardize medical literature searches in PubMed.

Instructions

Query the curated ICD/MeSH crosswalk in one explicit direction.

Use icd_to_mesh with one complete ICD-9-CM or ICD-10-CM code, or mesh_to_icd with a MeSH term. The returned mapping is a limited convenience crosswalk, not a substitute for a current licensed UMLS terminology service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / code
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Code"
-}
    • addedInput schema / properties / direction
      Added value: +{
+  "enum": [
+    "icd_to_mesh",
+    "mesh_to_icd"
+  ],
+  "title": "Direction",
+  "type": "string"
+}
    • removedInput schema / properties / mesh_term
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Mesh Term"
-}
    • addedInput schema / properties / value
      Added value: +{
+  "maxLength": 500,
+  "minLength": 1,
+  "title": "Value",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "direction",
+  "value"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "convert_icd_meshOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.5.16

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world traits, so the bar is lower. The description adds genuinely useful context beyond them: the crosswalk is 'curated' and a 'limited convenience' mapping, disclosing data-quality/coverage limitations an agent would not otherwise know.

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?

Two tight sentences, front-loaded with the core purpose and followed by direction routing and a limitation. No filler; every clause carries 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?

No output schema exists, so the description bears the burden of describing returns. It gestures at the mapping quality ('limited convenience crosswalk') but never describes the shape of the result (single term vs. list, ambiguity handling), leaving a gap for a mapping tool.

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?

Schema description coverage is 0%, so the description must compensate, and it does: it explains that 'value' must be one complete ICD-9-CM or ICD-10-CM code for the icd_to_mesh direction or a MeSH term for mesh_to_icd. It does not address code formatting (dots) or the 500-char limit, so it is not exhaustive.

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 and resource: 'Query the curated ICD/MeSH crosswalk in one explicit direction.' An agent immediately knows this maps between ICD and MeSH vocabularies, and no sibling tool covers terminology crosswalking, so differentiation is moot.

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 routes each enum value: 'icd_to_mesh' with a complete ICD-9-CM/ICD-10-CM code, 'mesh_to_icd' with a MeSH term. It also adds a when-not caveat (not a substitute for a licensed UMLS service), which is exactly the kind of selection guidance an agent needs.

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

Deploy Server

Other Tools