Skip to main content
Glama

normalize_allele

Read-onlyIdempotent

Normalize one reported HLA allele name (any era or reporting shorthand: legacy A0101, Cw0702 or Cw07:02, G/P group names, A02:XX, two-field A02:01g, optional HLA- prefix) to current 2-field form, with G group, P group, serologic equivalent, and flags. NMDP MAC codes (A02:AB) are recognised but not expanded (flag mac_code). A name that does not exist comes back UNRESOLVABLE (flag nonexistent_allele), never corrected to a nearby real one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "normalize_allele"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesOne reported HLA allele name, any nomenclature era. An allele string only, never a patient name, medical record number or other identifier.

Output Schema

NameRequiredDescriptionDefault
flagsYese.g. deprecated_name, legacy_rollover (a pre-2010 rollover name such as A*9201, resolved through the official 2010 mapping to A*02:101), nonexistent_allele, null_allele, g_group_name, p_group_name, xx_code, lg_notation, mac_code.
g_groupYesG group; NONE (no group), AMBIGUOUS (members differ) or UNRESOLVABLE.
reportedYesThe input, verbatim.
current_nameYesCurrent full name in the pinned release, or UNRESOLVABLE.
allele_2fieldYesCurrent 2-field form, or UNRESOLVABLE. Never present an UNRESOLVABLE name as an allele.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / flags / description
      Previous value: -"e.g. deprecated_name, nonexistent_allele, null_allele, g_group_name, p_group_name, xx_code, lg_notation, mac_code."New value: +"e.g. deprecated_name, legacy_rollover (a pre-2010 rollover name such as A*9201, resolved through the official 2010 mapping to A*02:101), nonexistent_allele, null_allele, g_group_name, p_group_name, xx_code, lg_notation, mac_code."
  2. Changed1 schema field changed
    • changedOutput schema / properties / flags / description
      Previous value: -"e.g. deprecated_name, nonexistent_allele, null_allele."New value: +"e.g. deprecated_name, nonexistent_allele, null_allele, g_group_name, p_group_name, xx_code, lg_notation, mac_code."
  3. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Reported allele name, any nomenclature era."New value: +"One reported HLA allele name, any nomenclature era. An allele string only, never a patient name, medical record number or other identifier."
  4. First observed

TDQS

A4.2/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 behavior, but the description adds real semantics beyond them: MAC codes are flagged rather than expanded, unparseable names return UNRESOLVABLE with a nonexistent_allele flag, and no nearest-match correction is ever applied. Those failure-mode guarantees are the key thing an agent needs, though input-validation errors (e.g. over-length or non-allele text) are not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the verb and resource, with no filler. The only minor waste is the trailing enumeration of outputs (G group, P group, serologic equivalent, flags), which an output schema already carries.

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 one-parameter, annotated tool with an output schema, the description covers everything an agent needs: accepted input dialects, the MAC-code limitation, and the failure semantics for nonexistent names. Return-value detail is rightly left to the output schema, so nothing material is missing.

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?

The single parameter is fully documented in the schema, so the baseline is 3, but the description earns more by spelling out which input dialects are actually accepted (legacy, Cw* forms, G/P groups, XX wildcards, g-suffixed two-field, HLA- prefix). It also reinforces the negative constraint that only an allele string is valid, not a patient identifier.

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 (normalize) and resource (one reported HLA allele name) and enumerates the accepted input eras/shorthands (legacy A*0101, Cw*07:02, G/P group names, A*02:XX, A*02:01g, optional HLA- prefix). This is clearly a single-allele normalizer, distinguishable from siblings like translate_names, allele_info or validate_gl_string without opening a schema.

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?

Scope is implied clearly (exactly one allele name, any nomenclature era), and two boundaries are set: MAC codes are recognised but not expanded, and nonexistent names are not corrected. However, it never names an alternative tool or states when to prefer a different sibling (e.g. for batch or full allele lookup), so routing guidance remains inferred rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.