Skip to main content
Glama

xo_v2v_status

Check a running V2V migration's progress, current phase, and estimated completion time using its task ID, with an optional target gateway.

Instructions

Check the status of a running V2V migration (progress %, phase, ETA).

Args: task_id: Migration task ID (returned by xo_v2v_migrate). gateway_id: Target gateway (optional).

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": {
      "task_id": "<task_id>"
    },
    "name": "xo_v2v_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose the shape of the payload (progress, phase, ETA), but says nothing about terminal states (success/failure), polling cadence, or whether the call has side effects — for a status probe the read-only nature is inferable but undeclared.

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?

Two lines, front-loaded with the purpose, followed by a compact Args block — nothing extraneous. The parenthetical field list is efficient; only the standard boilerplate formatting keeps it from being exemplary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description has to cover both behavior and return semantics and only partially does so. Returned fields are sketched, but terminal-state reporting, failure modes, and the semantics of the optional gateway selector are missing for a tool whose entire job is reporting state.

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 0%, so the description must document both params. It does anchor task_id well by naming its producer (xo_v2v_migrate), but gateway_id is dismissed as merely "(optional)" with no indication of when a caller must supply it or what it changes about the query.

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?

States a specific verb and resource ("Check the status of a running V2V migration") and names the returned fields (progress %, phase, ETA), which separates it from the launcher xo_v2v_migrate. It stops short of an explicit contrast with the sibling, but the intent is unambiguous.

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?

Usage context is clear: it operates on a migration already started, and the task_id is explicitly tied back to xo_v2v_migrate. No exclusions or when-not conditions are given, and it does not say what to do for finished or failed migrations.

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

Deploy Server

Other Tools