central-mcp

Overview Schema Source Related Servers Discussions Admin

tail_dispatch

Read a running dispatch's output so far without waiting for it to finish. Check progress, spot quiet agents, and fetch only new lines since your last call.

Instructions

Read what a dispatch has printed so far, without waiting for it to finish.

check_dispatch returns output only after the agent exits. Use this while a dispatch is still running — to answer "what is it doing right now?", or to look closer when output.state is quiet.

Arguments: dispatch_id — the id dispatch returned. since — the next_since value from your previous call, to get only newer lines. Omit it on the first call. A plain ISO 8601 timestamp is accepted too. max_lines — most lines to return (default 50). When more are new, you get the newest and skipped counts the rest.

Returns lines (oldest first; each has ts, stream, agent, text), skipped, next_since, the dispatch status, and output:

state streaming | quiet | no_output_yet | exit_only last_output_age_sec seconds since the newest line output_lines lines emitted so far

Read output.state before you report on a silent dispatch:

exit_only — this agent prints only when it exits (claude does). No lines is its normal state. Do not report it as stuck.
quiet — the agent printed before and has printed nothing for 15 minutes. It may be stuck. Tell the user; do not cancel on your own.
no_output_yet — nothing printed so far. Report the elapsed time.

Lines are raw agent output (often JSON events) — summarize them for the user; do not paste them. Once status is no longer running, call check_dispatch for the final result.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	No
`max_lines`	No
`dispatch_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.21.0Oct 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations exist, so the description bears the full load and delivers substantial context: the four output.state values, their meanings, and explicit 'do not' guidance (don't report exit_only as stuck, don't cancel quietly on your own). It stops short of covering auth or rate-limit behavior, but is unusually rich for a read tool.

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 purpose, then usage, then arguments, then return shape — a clean, scannable structure. It is somewhat long for a three-parameter read tool, but nearly every sentence adds decision-relevant detail rather than filler.

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, the description needn't enumerate return fields, yet it adds the interpretation layer the schema can't provide (state semantics, last_output_age_sec, and the correct next action). Nothing an agent needs to call or interpret this tool is missing.

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 coverage is 0%, so the description carries the full parameter burden and does so: dispatch_id is tied to dispatch's return, since is tied to next_since (with ISO 8601 fallback and omit-on-first-call guidance), and max_lines documents the default, the newest-first behavior, and the skipped counter.

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?

Opening sentence states a specific verb and resource ('Read what a dispatch has printed so far') plus the defining constraint ('without waiting for it to finish'). It immediately distinguishes itself from the sibling check_dispatch, which is named explicitly.

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?

Gives explicit when-to-use ('while a dispatch is still running'), when-to-prefer-the-alternative ('check_dispatch returns output only after the agent exits'), and routes the agent onward once status leaves running. It also names the trigger condition ('when output.state is quiet').

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