Skip to main content
Glama

cid10_search

Read-onlyIdempotent

Search the Brazilian CID-10 by Portuguese text to find diagnostic codes for SUS/ANVISA contexts, clinical documentation, and epidemiology.

Instructions

Search the Brazilian CID-10 (Classificação Estatística Internacional de Doenças, 10ª Revisão) by Portuguese text.

Use this tool to:

  • Find CID-10 codes for Brazilian SUS / ANVISA contexts ("infarto", "diabetes", "tuberculose")

  • Look up the official Portuguese (CBCD/USP) translation of a clinical term

  • Locate codes for billing, epidemiology, and clinical documentation in Brazil

Returns matches from CID-10 categories (3-char) and/or subcategories (4-char). Search is diacritic-insensitive: typing "infeccoes" matches "infecções". This tool searches the Brazilian Portuguese CID-10 V2008 — for the international ICD-11 (current WHO revision, in English by default), use icd11_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term in Portuguese (e.g., "diabetes", "infarto", "tuberculose")
levelNoRestrict search to 3-char categories, 4-char subcategories, or both. Default: allall
max_resultsNoMaximum number of results (1-100). Default: 25

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
levelYes
total_countYes
shown_countYes
hitsYes
Behavior4/5

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

Annotations already cover safety (readOnlyHint, etc.). Description adds diacritic-insensitivity and region/version specificity (CID-10 V2008 Brazilian Portuguese). No contradictions; additional behavioral details are useful but not extensive.

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 well-structured paragraphs with a clear first sentence, bullet-like list, and concise additional details. No redundant or unnecessary text.

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?

Given the presence of output schema and annotations, the description fully covers the tool's purpose, usage, search behavior, and alternatives. No gaps remain for an agent to understand when and how to invoke it.

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%, so baseline is 3. The description explains the query language and result structure (categories/subcategories), but does not add significant meaning beyond the schema's parameter descriptions.

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 Brazilian CID-10 by Portuguese text, lists specific use cases, and distinguishes from icd11_search for international ICD-11. This provides a specific verb+resource and differentiates from siblings.

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 states when to use (Brazilian contexts, billing, epidemiology) and when not to (international ICD-11, pointing to icd11_search). Provides clear alternative tool.

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