Skip to main content
Glama
Sign In
spillway-mcp

spillway-mcp

by Secret-art-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agy_job_result

Read-onlyIdempotent

Fetch stored output or live status for an Antigravity job by job_id or "latest" to collect results from long-running delegated research, swarm, edit, or follow-up calls that hit their soft timeout.

Instructions

Fetch the stored output or live status of an Antigravity job by job_id (or "latest"). WHEN TO USE: Retrieving the result of a long-running agy_delegate_research, agy_spawn_swarm, agy_delegate_edit, or agy_session_followup call that returned "still running, job <id>..." after reaching the soft budget (default 540s). DO NOT USE FOR: Starting a new research or edit task. RETURNS: The full completed subagent response and session telemetry if finished (done / failed / cancelled / timed_out), or "still running, job <id>, started <time>, elapsed <s>s; fetch with agy_job_result <id>" if still in flight.

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": {
      "job_id": "<job_id>"
    },
    "name": "agy_job_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id returned when a run exceeded the soft timeout (or listed in agy_status.agy_process_queue), or "latest" for the most recent job.
wait_msNoOptional milliseconds to wait for completion if the job is still running (default 0 for instant check; max 540000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive, yet the description still adds real value: terminal states (done/failed/cancelled/timed_out), the 540s soft budget, and the exact still-running sentinel an agent will see. It does not mention that wait_ms allows blocking up to 540s, so the polling-vs-wait choice is left to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then segmented into WHEN TO USE / DO NOT USE FOR / RETURNS. Every sentence carries distinct routing or return-value information with no padding.

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 RETURNS block does the necessary work by describing both the completed payload and the in-flight sentinel. The only gap is the absence of guidance on using wait_ms versus re-polling, which an agent must infer from the input schema.

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 100%, so both params are already fully documented, including the 'latest' sentinel and wait_ms bounds. The description only repeats the job_id/'latest' behavior, adding no syntax or format detail beyond the schema.

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 ('fetch the stored output or live status of an Antigravity job') plus the lookup key ('by job_id or "latest"'). It is clearly distinguishable from siblings like agy_delegate_research or agy_status, which start work or list the queue rather than retrieve a single job's payload.

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?

An explicit WHEN TO USE clause names the four sibling tools whose soft-budget output produces a job id, and DO NOT USE FOR explicitly excludes starting new work. The condition that selects this tool (a prior run returned 'still running, job <id>') is stated verbatim.

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