Skip to main content
Glama

Clinicaltables

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Icd9cm

icd9cm
Read-onlyIdempotent

"Old ICD-9 code for [diagnosis]" / "pre-2015 diagnosis codes" — search legacy ICD-9-CM diagnostic codes. Use ONLY when working with pre-2015 US clinical records; new claims must use icd10cm. Same shape as icd10cm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dfNoComma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name.
efNoComma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov.
countNoMaximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing.
termsYesSearch query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "asthma".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "count": 3,
+    "terms": "asthma"
+  }
+]
  2. Changed7 schema fields changed
    • addedInput schema / properties / count / default
      Added value: +7
    • addedInput schema / properties / count / description
      Added value: +"Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing."
    • addedInput schema / properties / count / maximum
      Added value: +500
    • addedInput schema / properties / count / minimum
      Added value: +1
    • addedInput schema / properties / df / description
      Added value: +"Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name."
    • addedInput schema / properties / ef / description
      Added value: +"Comma-separated extra fields to include per match. Field names vary per table; check NLM docs at clinicaltables.nlm.nih.gov."
    • addedInput schema / properties / terms / description
      Added value: +"Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: \"asthma\"."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and mutability. The description adds valuable context about the temporal scope (pre-2015) and the data domain, which goes beyond annotations. It also hints at behavioral similarity to icd10cm, which is useful but not exhaustive regarding return format or pagination.

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 with no redundancy. It front-loads the core purpose, then immediately provides usage constraints, and ends with a helpful shape reference. Every clause earns its place, making it highly efficient.

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 search tool with a well-documented schema and safety annotations, the description covers when to use it, what it does, and points to icd10cm for shape. It does not explicitly describe return structure or search semantics, but those are either in the schema or implied by the shape reference. Given the tool's moderate complexity, this is nearly complete.

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% description coverage for all four parameters, including detailed explanations for 'terms', 'df', 'ef', and 'count'. The description itself does not add parameter-specific details beyond the schema, but it references 'Same shape as icd10cm', which is an indirect pointer. Since the schema is thorough, a baseline of 3 is appropriate.

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 searches legacy ICD-9-CM diagnostic codes, with a specific verb and resource. It explicitly contrasts with icd10cm, making it distinct from its sibling. The phrasing 'Old ICD-9 code for [diagnosis]' and 'pre-2015 diagnosis codes' immediately conveys the scope.

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?

The description gives explicit usage guidance: 'Use ONLY when working with pre-2015 US clinical records; new claims must use icd10cm.' It names the alternative (icd10cm) and the condition for selection, leaving no ambiguity. The phrase 'Same shape as icd10cm' further informs usage patterns.

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

All Clinicaltables toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources