Skip to main content
Glama
Sign In
agy-agent-mcp

agy-agent-mcp

by a4amk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Watch live or recent task stream transcript

watch_task

Reads the transcript tail of an agy run to check progress, wait for completion, or cancel an owned task, returning final results and failure reasons.

Instructions

Read transcript tail of an agy run (snapshot, not follow; no args = latest run). Digest: steps (50 most recent), step_count (total; step_count > steps.length means clipped), phase, elapsed_seconds, usage_latest, content (raw tail). Finished runs carry complete final result (failed run says why). wait: true blocks until finished in one call (not combinable with cancel; cannot await foreign run). cancel: true stops owned run (foreign/ambiguous reported ignored with hint).

Input Schema

NameRequiredDescriptionDefault
waitNoBlock until finished and return result in one call. Incompatible with cancel; cannot await foreign run.
cancelNoStop running task owned by this process and report cancelled.
tail_linesNoTrailing lines (1..2000, default 400; 0 returns all, capped at 200k chars).
stream_fileNoTranscript or task ID. Omit for latest run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • addedInput schema / properties / cancel
      Added value: +{
+  "description": "Stop running task owned by this process and report cancelled.",
+  "type": "boolean"
+}
    • changedInput schema / properties / stream_file / description
      Previous value: -"Stream transcript to read. Omit for the latest task_<id>.stream in AGY_MCP_STATE_DIR. Accepted forms: an absolute path under AGY_MCP_STATE_DIR, a bare file name like \"task_f8870173.stream\", or a task id like \"task_f8870173\" / \"f8870173\"."New value: +"Transcript or task ID. Omit for latest run."
    • changedInput schema / properties / tail_lines / description
      Previous value: -"Number of trailing lines to return (1..2000, default 400; 0 returns the full transcript, hard-capped at 200,000 chars)."New value: +"Trailing lines (1..2000, default 400; 0 returns all, capped at 200k chars)."
    • addedInput schema / properties / wait
      Added value: +{
+  "description": "Block until finished and return result in one call. Incompatible with cancel; cannot await foreign run.",
+  "type": "boolean"
+}
  2. First observedv0.2.1

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses snapshot semantics, digest contents including clipping behavior, final-result availability for finished runs, blocking behavior for wait, and ownership rules for cancel. It also notes that foreign/ambiguous cancel requests are ignored with a hint.

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?

Information is front-loaded with the core purpose first, then digest contents, then wait/cancel behavior. The dense single paragraph is efficient and every sentence adds value, though the density slightly reduces scannability.

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?

No output schema exists, and the description fully explains the return digest (steps, step_count with clipping indicator, phase, elapsed_seconds, usage_latest, content). It covers everything an agent needs to call and interpret the tool.

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 coverage is 100%, so the schema already documents all four parameters. The description adds a few useful details (no args means latest run, wait/cancel interaction, tail digest meaning) but does not meaningfully extend parameter semantics beyond the schema baseline.

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 (read) and resource (transcript tail of an agy run), with scope details like snapshot-not-follow and no-args-latest. An agent can distinguish it from list_agents or general_task 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?

Explains key usage conditions: omit args for latest run, use wait:true to block until finished, cancel:true to stop owned runs, and notes incompatibility between wait and cancel. It lacks explicit routing against siblings, but gives clear operational context.

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