Skip to main content
Glama

about

Read-onlyIdempotent

What this server is and is not, what to send it, benchmark evidence for why to use it, the beta state, and terms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
apiNo
whyNo
betaNo
codeNo
demoNo
nameYes
scopeNo
agentsNo
inputsNo
limitsNo
releaseYesIPD-IMGT/HLA release every verdict was computed against.
beta_keyNo
researchNo
commercialNo
disclaimerNo
beta_signupNo
differentiationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / differentiation
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / research
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / limits
      Added value: +{
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedOutput schema / properties / inputs
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / scope
      Added value: +{
      +  "type": "string"
      +}
  5. Changed3 schema fields changed
    • addedOutput schema / properties / beta
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / beta_key
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / beta_signup
      Added value: +{
      +  "type": "string"
      +}
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered without description help. The description adds that the content is partly evaluative and partly legal (benchmark evidence, beta state, terms), which is useful context beyond the annotations, but it says nothing about size, format, or stability of the returned document.

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?

It is a single compact sentence with no filler, and the most important item ("what this server is and is not") is front-loaded. The comma-separated content list is slightly inventory-like rather than prose, but nothing is redundant.

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 zero-parameter informational tool with an output schema present, the description only needs to say what the document covers, and it does so across five distinct topics. Return-value structure is legitimately left to the output schema, so no meaningful gap remains.

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?

There are zero parameters, so the baseline is 4 and no parameter explanation is required. The schema is closed (additionalProperties: false) and fully described, leaving nothing for the description to compensate for.

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 enumerates the concrete contents (server scope, what to send it, benchmark evidence, beta state, terms), which makes it clear this is the server's own orientation/documentation tool. It never uses an explicit verb like "returns" or "describes," but the enumerated payload is specific enough to separate it from every sibling, all of which are functional allele/pgx/donor tools.

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?

Usage is only implied: "benchmark evidence for why to use it" and "the beta state" hint that this is read first when deciding whether to adopt the server. There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named — though with a zero-parameter info tool the alternatives are effectively nonexistent.

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.