Skip to main content
Glama

verify_text

Read-onlyIdempotent

Scan HLA typing report text, or model output about HLA, for allele-shaped tokens and classify each one: valid / legacy spelling such as A0201 or Cw0702 (valid, with modern form and flag deprecated_name) / G-P group / deleted (with successor) / hallucinated (an invented name, never passed as real) / NMDP MAC code (seen, not expanded) / KIR name (out of scope, not checked); a valid token with fewer than four fields carries resolution, what that field count does and does not distinguish. Nomenclature checking against a pinned IPD-IMGT/HLA release, not interpretation of a case. Use on any AI-generated or transcribed content mentioning HLA. Send the HLA content only, with patient identifiers removed first.

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": {
      "text": "<text>"
    },
    "name": "verify_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesHLA typing report text, or model output about HLA typing, to scan for allele names. Send the HLA content only: strip patient names, medical record numbers, dates of birth, accession and case identifiers, and any other patient details before sending. The caller is responsible for de-identifying the text; this service neither needs nor wants identifiers and does not store request bodies.

Output Schema

NameRequiredDescriptionDefault
cleanYesThe guardrail: true only when no token is hallucinated, fabricated_group or deleted. Gate on this before presenting the text. NMDP multiple allele codes (counts.mac_code) and KIR allele names (counts.out_of_scope) are not checked — treat them as unverified.
countsYesNumber of distinct tokens per status.
tokensYesEach distinct allele-shaped token found, sorted by token.
releaseYesIPD-IMGT/HLA release every verdict was computed against.
attributionNoData attribution (IPD-IMGT/HLA, CC-BY-ND).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / tokens / items / 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"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / tokens / items / properties / status / description
      Previous value: -"valid: assigned (or a valid prefix; A*02:XX and two-field A*02:01g are checked by the name they abbreviate); group: a real G/P group; deleted: no longer current (see successor); fabricated_group: G/P-shaped but no such group; hallucinated: never existed in any release; mac_code: an NMDP multiple allele code, reporting shorthand this service does not expand; out_of_scope: a KIR allele name (IPD-KIR), outside IPD-IMGT/HLA and not checked."New value: +"valid: assigned (or a valid prefix; A*02:XX and two-field A*02:01g are checked by the name they abbreviate, and a legacy spelling such as A*0201, Cw*0702 or Cw*07:02 by the current name it stands for, with flag deprecated_name); group: a real G/P group; deleted: no longer current (see successor); fabricated_group: G/P-shaped but no such group; hallucinated: never existed in any release; mac_code: an NMDP multiple allele code, reporting shorthand this service does not expand; out_of_scope: a KIR allele name (IPD-KIR), outside IPD-IMGT/HLA and not checked."
  3. Changed5 schema fields changed
    • changedOutput schema / properties / clean / description
      Previous value: -"The guardrail: true only when no token is hallucinated, fabricated_group or deleted. Gate on this before presenting the text. NMDP multiple allele codes (counts.mac_code) are not checked — treat them as unverified."New value: +"The guardrail: true only when no token is hallucinated, fabricated_group or deleted. Gate on this before presenting the text. NMDP multiple allele codes (counts.mac_code) and KIR allele names (counts.out_of_scope) are not checked — treat them as unverified."
    • addedOutput schema / properties / counts / properties / out_of_scope
      Added value: +{
      +  "description": "KIR allele names (KIR3DL1*001) seen; a gene family outside IPD-IMGT/HLA, not checked.",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / counts / required
      Previous value: -[
      -  "valid",
      -  "deleted",
      -  "group",
      -  "fabricated_group",
      -  "hallucinated",
      -  "mac_code"
      -]New value: +[
      +  "valid",
      +  "deleted",
      +  "group",
      +  "fabricated_group",
      +  "hallucinated",
      +  "mac_code",
      +  "out_of_scope"
      +]
    • changedOutput schema / properties / tokens / items / properties / status / description
      Previous value: -"valid: assigned (or a valid prefix; A*02:XX and two-field A*02:01g are checked by the name they abbreviate); group: a real G/P group; deleted: no longer current (see successor); fabricated_group: G/P-shaped but no such group; hallucinated: never existed in any release; mac_code: an NMDP multiple allele code, reporting shorthand this service does not expand."New value: +"valid: assigned (or a valid prefix; A*02:XX and two-field A*02:01g are checked by the name they abbreviate); group: a real G/P group; deleted: no longer current (see successor); fabricated_group: G/P-shaped but no such group; hallucinated: never existed in any release; mac_code: an NMDP multiple allele code, reporting shorthand this service does not expand; out_of_scope: a KIR allele name (IPD-KIR), outside IPD-IMGT/HLA and not checked."
    • changedOutput schema / properties / tokens / items / properties / status / enum
      Previous value: -[
      -  "valid",
      -  "group",
      -  "deleted",
      -  "fabricated_group",
      -  "hallucinated",
      -  "mac_code"
      -]New value: +[
      +  "valid",
      +  "group",
      +  "deleted",
      +  "fabricated_group",
      +  "hallucinated",
      +  "mac_code",
      +  "out_of_scope"
      +]
  4. Changed5 schema fields changed
    • changedOutput schema / properties / clean / description
      Previous value: -"The guardrail: true only when no token is hallucinated, fabricated_group or deleted. Gate on this before presenting the text."New value: +"The guardrail: true only when no token is hallucinated, fabricated_group or deleted. Gate on this before presenting the text. NMDP multiple allele codes (counts.mac_code) are not checked — treat them as unverified."
    • addedOutput schema / properties / counts / properties / mac_code
      Added value: +{
      +  "description": "NMDP multiple allele codes (A*02:AB) seen but not expanded.",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / counts / required
      Previous value: -[
      -  "valid",
      -  "deleted",
      -  "group",
      -  "fabricated_group",
      -  "hallucinated"
      -]New value: +[
      +  "valid",
      +  "deleted",
      +  "group",
      +  "fabricated_group",
      +  "hallucinated",
      +  "mac_code"
      +]
    • changedOutput schema / properties / tokens / items / properties / status / description
      Previous value: -"valid: assigned (or a valid prefix); group: a real G/P group; deleted: no longer current (see successor); fabricated_group: G/P-shaped but no such group; hallucinated: never existed in any release."New value: +"valid: assigned (or a valid prefix; A*02:XX and two-field A*02:01g are checked by the name they abbreviate); group: a real G/P group; deleted: no longer current (see successor); fabricated_group: G/P-shaped but no such group; hallucinated: never existed in any release; mac_code: an NMDP multiple allele code, reporting shorthand this service does not expand."
    • changedOutput schema / properties / tokens / items / properties / status / enum
      Previous value: -[
      -  "valid",
      -  "group",
      -  "deleted",
      -  "fabricated_group",
      -  "hallucinated"
      -]New value: +[
      +  "valid",
      +  "group",
      +  "deleted",
      +  "fabricated_group",
      +  "hallucinated",
      +  "mac_code"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / text / description
      Previous value: -"Free text to scan."New value: +"HLA typing report text, or model output about HLA typing, to scan for allele names. Send the HLA content only: strip patient names, medical record numbers, dates of birth, accession and case identifiers, and any other patient details before sending. The caller is responsible for de-identifying the text; this service neither needs nor wants identifiers and does not store request bodies."
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and closed-world, and the description still adds substantial behavior: what each classification means, that legacy spellings return the modern form plus a deprecated_name flag, that deleted names return a successor, that MAC codes are seen but not expanded, that KIR is out of scope, and that a sub-four-field token carries resolution limits. It also pins the check to a specific IPD-IMGT/HLA release, which tells the agent results are release-dependent.

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?

Front-loaded with the action and scope, then the classification taxonomy, then usage and the privacy caveat. The middle enumeration is a dense slash-delimited run-on that takes effort to parse, but nearly every clause carries distinct information rather than filler.

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?

An output schema exists, so return values need no explanation, and the description covers scope, limits, release pinning, and de-identification obligations. It stops short of mentioning practical constraints the agent may hit, such as the 200,000-character input ceiling or behavior on mixed or partial input.

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?

There is one parameter with 100% schema coverage, and the schema already documents the de-identification requirement in full. The description restates "send the HLA content only, with patient identifiers removed first" without adding format or sizing guidance beyond what the schema provides, so the baseline 3 applies.

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 pair (scan and classify) over a specific resource (HLA typing report text or model output about HLA), then enumerates the exact output classes: valid, legacy spelling, G-P group, deleted, hallucinated, NMDP MAC, KIR. It also draws an explicit boundary against interpretation of a case, which separates it from sibling tools like check_typing or allele_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use on any AI-generated or transcribed content mentioning HLA" gives a clear positive trigger, and "not interpretation of a case" gives a clear exclusion. It does not name an alternative sibling (e.g. normalize_allele for a single known allele), so the routing is strong but not exhaustive.

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.