Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Wait for Cyclone job

cyclone_job
Read-onlyIdempotent

Wait for and read a Cyclone job by dispatch_id, returning status, outcome, pushed commit, and changed files; use timeout_s to poll until done or read once with 0.

Instructions

Wait for a Cyclone job started with cyclone_start, by its dispatch_id, and read it: queued, running, pushed, completed or failed, with the outcome, detail, pushed commit and changed files. timeout_s (default 45, max 100) waits until the job is pushed, completed or failed, or the time is up; 0 reads it once. While it is queued or running, call again with the same dispatch_id.

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": {
      "dispatch_id": "<dispatch_id>"
    },
    "name": "cyclone_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_sNo
dispatch_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description adds genuinely new behavior: the polling loop pattern, the wait-until condition (pushed/completed/failed), the default and maximum timeout, and the fields returned. It stops short of describing what happens on an unknown or expired dispatch_id, but covers the operational profile well.

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 outcome and identifier, then timeout semantics, then the retry rule. Dense but every clause carries information; the middle clause about states and returned fields is a slightly long run-on but not wasteful.

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?

With no output schema, the description enumerates the job states and returned data (outcome, detail, pushed commit, changed files), and explains the timeout contract. A reader has everything needed to poll correctly; only edge-case behavior for invalid or missing dispatch_ids is unstated.

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?

Schema description coverage is 0%, so the description must carry the load and it does: dispatch_id is the job id from cyclone_start, and timeout_s has a default of 45, a cap of 100, a wait-until condition, and a special zero value meaning read-once. That is meaning well beyond the bare integer/uuid types.

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 and resource ('Wait for a Cyclone job') with the exact identifier to use (dispatch_id) and names the originating sibling cyclone_start. An agent can distinguish it from cyclone_start or queue_status without opening the schema.

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?

Explicitly says to call again with the same dispatch_id while the job is queued or running, and that timeout_s=0 performs a single non-blocking read. This gives clear when-to-call guidance, though it does not state when another tool (e.g. queue_status) would be preferred.

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