ImmunoGraph MCP

calculate_population_coverage

Read-onlyIdempotent

Estimate HLA population coverage for supplied peptide-allele associations using an authoritative IEDB service or allowed fixture; use when allele restrictions and population IDs are known.

Instructions

Estimate HLA population coverage for supplied peptide-allele associations using a configured authoritative IEDB service or an explicitly allowed exact fixture. Use when the allele restrictions and population IDs are known; use calculate_synthetic_population_coverage only for demonstrations. LIVE_ONLY requires the live service and the result carries source provenance.

Input Schema

Name	Required	Description	Default
`runId`	No	Caller-chosen identifier linking this call to one research run.	interactive-run
`classMode`	No	Whether coverage uses class-I, class-II, or combined associations.	COMBINED
`associations`	Yes	Peptide-to-HLA restrictions used for population coverage calculation.
`populationIds`	Yes	Population identifiers requested from the coverage source or synthetic dataset.
`fallbackPolicy`	No	Allowed source order; LIVE_ONLY forbids cache and fixture substitution, FIXTURE_ONLY forbids live calls.	LIVE_THEN_CACHE_THEN_FIXTURE

Output Schema

Name	Required	Description
`ok`	Yes	Whether execution completed successfully.
`data`	No	Tool-specific result fields on success.
`meta`	Yes	Run identifiers, timings, and input/output hashes.
`error`	No	Structured failure on unsuccessful execution.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.2.1Oct 31, 2026

addedInput schema / properties / associations / description

Added value: +"Peptide-to-HLA restrictions used for population coverage calculation."

addedInput schema / properties / classMode / description

Added value: +"Whether coverage uses class-I, class-II, or combined associations."

addedInput schema / properties / fallbackPolicy / description

Added value: +"Allowed source order; LIVE_ONLY forbids cache and fixture substitution, FIXTURE_ONLY forbids live calls."

addedInput schema / properties / populationIds / description

Added value: +"Population identifiers requested from the coverage source or synthetic dataset."

addedInput schema / properties / runId / description

Added value: +"Caller-chosen identifier linking this call to one research run."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "Tool-specific result fields on success.",
+      "properties": {},
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": false,
+      "description": "Structured failure on unsuccessful execution.",
+      "properties": {
+        "category": {
+          "type": "string"
+        },
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "code",
+        "category",
+        "message",
+        "retryable"
+      ],
+      "type": "object"
+    },
+    "meta": {
+      "additionalProperties": {},
+      "description": "Run identifiers, timings, and input/output hashes.",
+      "properties": {
+        "completedAt": {
+          "type": "string"
+        },
+        "durationMs": {
+          "type": "number"
+        },
+        "inputHash": {
+          "type": "string"
+        },
+        "outputHash": {
+          "type": "string"
+        },
+        "requestId": {
+          "type": "string"
+        },
+        "runId": {
+          "type": "string"
+        },
+        "startedAt": {
+          "type": "string"
+        },
+        "toolName": {
+          "type": "string"
+        },
+        "toolVersion": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "requestId",
+        "runId",
+        "toolName",
+        "toolVersion",
+        "startedAt",
+        "inputHash"
+      ],
+      "type": "object"
+    },
+    "ok": {
+      "description": "Whether execution completed successfully.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "meta"
+  ],
+  "type": "object"
+}

First observedv0.2.0Oct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations cover read-only/idempotent safety, and the description adds real behavioral context beyond them: results carry source provenance, and LIVE_ONLY mandates the live service with no cache/fixture substitution. It stops short of describing failure behavior when the live service is unavailable or how partial coverage is reported.

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?

Three tight sentences: what it does first, when to use it second, source semantics last. There is no filler and no restatement of the tool name.

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?

With an output schema present, return values need no explanation, and annotations plus 100% schema coverage handle safety and parameters. The description supplies the remaining essentials: calculation scope, source authority, provenance, and sibling disambiguation.

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%, including the fallbackPolicy enum semantics, so the schema already carries parameter meanings and the baseline of 3 applies. The description only echoes the popular concept of 'allele restrictions and population IDs' without adding format or constraint detail beyond the schema.

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?

Specific verb+resource: 'Estimate HLA population coverage for supplied peptide-allele associations,' with the input domain narrowed to peptide-allele associations. It also explicitly contrasts with the sibling calculate_synthetic_population_coverage, so the agent can discriminate without opening either schema.

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?

States the precondition for use ('when the allele restrictions and population IDs are known') and routes the demonstration case to calculate_synthetic_population_coverage explicitly. The LIVE_ONLY/fixture caveat adds a second usage constraint rather than leaving it to inference.

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

Deploy Server