EVEE MCP Server

wait_for_variant_analysis

Polls EVEE until variant interpretation completes or times out, returning results with wait status. Use when interpretation is queued or processing.

Instructions

Poll EVEE's on-demand interpretation until it completes or times out.

Use this when get_variant reports interpretation.status as queued or processing. Returns the same curated variant summary as get_variant, plus a wait_status entry with attempts / elapsed_seconds. If the deadline hits before completion, call this tool again to keep polling.

Args: variant_id: Variant identifier in chr:pos:ref:alt format. timeout_seconds: Maximum wall-clock time to wait (clamped to [1, 60]). poll_interval_seconds: Delay between polls (clamped to [0.5, 10]).

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": {
      "variant_id": "<variant_id>"
    },
    "name": "wait_for_variant_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`variant_id`	Yes
`timeout_seconds`	No
`poll_interval_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

No annotations provided, but the description fully discloses polling behavior, timeout clamping, and return value details (wait_status entry). It is transparent about what happens on deadline hit.

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 well-structured with clear sections for purpose, usage, return, and argument details. It is slightly verbose but efficiently uses sentences without redundancy.

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 polling tool with no output schema, the description explains the return behavior (same as get_variant plus wait_status), all parameters, and usage context. It is fully self-contained and complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description explains each parameter thoroughly: variant_id format, timeout_seconds and poll_interval_seconds with clamping ranges and defaults, adding significant meaning.

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?

The description starts with 'Poll EVEE's on-demand interpretation until it completes or times out', providing a specific verb and resource. It clearly distinguishes from sibling tools like get_variant by indicating its polling nature.

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?

Explicitly states 'Use this when `get_variant` reports `interpretation.status` as queued or processing', including an alternative scenario. Also notes that if timeout occurs, call again, providing clear guidance.

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

Deploy Server