HLA-Verify

allele_info

Read-onlyIdempotent

Look up one name in the pinned release and return what it is: assigned (G/P group, first release, confirmed status, WMDA serology, null flag), valid_prefix (member count and sample, plus resolution: what a name with fewer than four fields does and does not distinguish), group (a G or P group name: member count and sample), or deleted (successor). Reported shorthands are accepted as /v1/normalize accepts them — legacy spellings (A0101, Cw0702, Cw07:02), the XX code (A02:XX), two-field A02:01g, an optional HLA- prefix — and answer with the facts of the name they stand for plus resolves_to and a flag (deprecated_name, xx_code, lg_notation); an NMDP multiple allele code (A02:AB) returns mac_code, recognised but not expanded. Not found if the name has never existed in any release.

Input Schema

Name	Required	Description	Default
`name`	Yes	An HLA allele name of any era: exact name, lower-resolution prefix, deleted name, G/P group, legacy colon-less name, XX code or lg notation. An allele string only, never a patient name, medical record number or other identifier.

Output Schema

Name	Required	Description
`name`	No
`note`	No	mac_code: what a multiple allele code is and why it is not expanded.
`flags`	No	Present for a shorthand: deprecated_name (legacy spelling: colon-less A0101, or the Cw locus label as in Cw07:02), xx_code, lg_notation, or mac_code. Absent for a plain name.
`detail`	No	Present only when the name is not assigned in this release (and then no other field is).
`status`	No	assigned: an exact allele in this release; valid_prefix: a lower-resolution prefix of assigned alleles; group: a G or P group name (see group_type); deleted: withdrawn or renamed (see successor); mac_code: an NMDP multiple allele code (A*02:AB), recognised but not expanded or checked.
`g_group`	No	assigned: G group, or null.
`ligands`	No	Class I (A/B/C) ligand facts, aggregated over member alleles: 'ambiguous' when members disagree, 'unknown' when no residue data.
`p_group`	No	assigned: P group, or null.
`release`	No	IPD-IMGT/HLA release every verdict was computed against.
`serology`	No	assigned: WMDA serologic equivalents by column (non-empty columns only), as published in rel_dna_ser.txt: an antigen number, '?' (undetermined equivalent) or '∅' (no serological equivalent, null). The lab tools report these as 'uncertain' and 'null'.
`confirmed`	No	assigned: confirmed (vs unconfirmed) allele.
`successor`	No	deleted: the current name, or null if none.
`group_type`	No	group: whether the name is a G group (identical exons 2+3 / exon 2) or a P group (identical peptide-binding domain).
`resolution`	No	Present on a name with fewer than four fields: what this resolution level does and does not distinguish.
`attribution`	No	Data attribution (IPD-IMGT/HLA, CC-BY-ND).
`null_allele`	No	assigned: true for an N (null, not expressed) allele.
`resolves_to`	No	Present when the name was a reported shorthand (legacy colon-less or Cw spelling, XX code, lg notation): the current-style name it stands for, whose facts this result carries.
`first_release`	No	assigned: first release the exact name appeared in.
`members_count`	No	valid_prefix / group: number of assigned alleles under the prefix or in the group.
`members_sample`	No	valid_prefix / group: up to 10 member alleles.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / properties / serology / description

Previous value: -"assigned: WMDA serologic equivalents by column (non-empty columns only)."New value: +"assigned: WMDA serologic equivalents by column (non-empty columns only), as published in rel_dna_ser.txt: an antigen number, '?' (undetermined equivalent) or '∅' (no serological equivalent, null). The lab tools report these as 'uncertain' and 'null'."

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / resolution

Added value: +{
+  "description": "Present on a name with fewer than four fields: what this resolution level does and does not distinguish.",
+  "properties": {
+    "distinguishes": {
+      "description": "What finer typing at the next field would add.",
+      "type": "string"
+    },
+    "fields": {
+      "description": "Number of colon-separated fields in the name.",
+      "enum": [
+        1,
+        2,
+        3
+      ],
+      "type": "integer"
+    },
+    "level": {
+      "description": "1 field: allele_group; 2: protein; 3: coding_sequence.",
+      "enum": [
+        "allele_group",
+        "protein",
+        "coding_sequence"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "fields",
+    "level",
+    "distinguishes"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 6, 2026

changedOutput schema / properties / flags / description

Previous value: -"Present for a shorthand: deprecated_name (legacy colon-less name), xx_code, lg_notation, or mac_code. Absent for a plain name."New value: +"Present for a shorthand: deprecated_name (legacy spelling: colon-less A*0101, or the Cw locus label as in Cw*07:02), xx_code, lg_notation, or mac_code. Absent for a plain name."

changedOutput schema / properties / resolves_to / description

Previous value: -"Present when the name was a reported shorthand (legacy colon-less, XX code, lg notation): the current-style name it stands for, whose facts this result carries."New value: +"Present when the name was a reported shorthand (legacy colon-less or Cw spelling, XX code, lg notation): the current-style name it stands for, whose facts this result carries."

Changed6 schema fields changedOct 6, 2026

changedInput schema / properties / name / description

Previous value: -"Exact HLA allele name, a lower-resolution prefix, or a deleted name. An allele string only, never a patient name, medical record number or other identifier."New value: +"An HLA allele name of any era: exact name, lower-resolution prefix, deleted name, G/P group, legacy colon-less name, XX code or lg notation. An allele string only, never a patient name, medical record number or other identifier."

addedOutput schema / properties / flags

Added value: +{
+  "description": "Present for a shorthand: deprecated_name (legacy colon-less name), xx_code, lg_notation, or mac_code. Absent for a plain name.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "mac_code: what a multiple allele code is and why it is not expanded.",
+  "type": "string"
+}

addedOutput schema / properties / resolves_to

Added value: +{
+  "description": "Present when the name was a reported shorthand (legacy colon-less, XX code, lg notation): the current-style name it stands for, whose facts this result carries.",
+  "type": "string"
+}

changedOutput schema / properties / status / description

Previous value: -"assigned: an exact allele in this release; valid_prefix: a lower-resolution prefix of assigned alleles; group: a G or P group name (see group_type); deleted: withdrawn or renamed (see successor)."New value: +"assigned: an exact allele in this release; valid_prefix: a lower-resolution prefix of assigned alleles; group: a G or P group name (see group_type); deleted: withdrawn or renamed (see successor); mac_code: an NMDP multiple allele code (A*02:AB), recognised but not expanded or checked."

changedOutput schema / properties / status / enum

Previous value: -[
-  "assigned",
-  "valid_prefix",
-  "group",
-  "deleted"
-]New value: +[
+  "assigned",
+  "valid_prefix",
+  "group",
+  "deleted",
+  "mac_code"
+]

Changed5 schema fields changedOct 4, 2026

addedOutput schema / properties / group_type

Added value: +{
+  "description": "group: whether the name is a G group (identical exons 2+3 / exon 2) or a P group (identical peptide-binding domain).",
+  "enum": [
+    "G",
+    "P"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / members_count / description

Previous value: -"valid_prefix: number of assigned alleles under the prefix."New value: +"valid_prefix / group: number of assigned alleles under the prefix or in the group."

changedOutput schema / properties / members_sample / description

Previous value: -"valid_prefix: up to 10 member alleles."New value: +"valid_prefix / group: up to 10 member alleles."

changedOutput schema / properties / status / description

Previous value: -"assigned: an exact allele in this release; valid_prefix: a lower-resolution prefix of assigned alleles; deleted: withdrawn or renamed (see successor)."New value: +"assigned: an exact allele in this release; valid_prefix: a lower-resolution prefix of assigned alleles; group: a G or P group name (see group_type); deleted: withdrawn or renamed (see successor)."

changedOutput schema / properties / status / enum

Previous value: -[
-  "assigned",
-  "valid_prefix",
-  "deleted"
-]New value: +[
+  "assigned",
+  "valid_prefix",
+  "group",
+  "deleted"
+]

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / name / description

Previous value: -"Exact allele, prefix, or deleted name."New value: +"Exact HLA allele name, a lower-resolution prefix, or a deleted name. An allele string only, never a patient name, medical record number or other identifier."

First observedSep 16, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With annotations already declaring readOnlyHint, openWorldHint=false and idempotentHint, the description still adds rich behavioral detail: it explains accepted shorthand formats, that NMDP multiple allele codes are recognized but not expanded, and that unknown names return 'Not found'. This goes well beyond the annotations and helps an agent predict results.

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?

The description is front-loaded with the core action and then enumerates return categories and shorthand rules. It is dense and somewhat long for a two-sentence description, but every clause conveys useful behavioral detail and nothing is repetitive filler.

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 single input parameter, the existence of an output schema, and the tool's read-only annotations, the description covers all the input semantics and result categories an agent needs. It also addresses shorthand acceptance and the not-found case, so no important piece 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?

Schema description coverage is 100%, so the schema already documents the single 'name' parameter. The description adds meaningful edge-case semantics, including legacy spellings, XX codes, lg notation, optional HLA- prefix, and the NMDP mac_code behavior, which is not fully captured in the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: look up one HLA name in the pinned release and return what kind of name it is (assigned, valid_prefix, group, deleted). The output categories are spelled out, so an agent knows precisely what the tool returns. It does not explicitly name or distinguish itself from sibling tools like allele_history or normalize_allele, keeping it from a 5.

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?

The description implies usage ('Look up one name in the pinned release') and gives conditions for shorthands and not-found results, but it never says when to choose this over alternatives such as allele_history or normalize_allele. There are no explicit when-not or alternative-routing statements.

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

All HLA-Verify tools Inspect

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.