Skip to main content
Glama

agy_status

Read-only

Inspect non-blocking status for one subagent or the entire Antigravity pool, including active count, queue length, live step progress, and circuit-breaker cooldown.

Instructions

Non-blocking status inspection for one agent or the entire Antigravity subagent pool (active count, queue length, live step progress, circuit-breaker cooldown status).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agy_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional specific agent_id; omit to list all agents in this session.
include_outputNoInclude last response text when inspecting status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the genuinely useful behavioral trait that the call is non-blocking and returns immediately, and it enumerates the observable state it reports (including circuit-breaker cooldown). It stops short of describing error or empty-pool behavior.

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?

A single front-loaded sentence with no filler: scope, non-blocking trait, and returned signals all appear immediately. Nothing is repeated from the name or annotations.

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?

This is a simple, zero-required-parameter read tool with no output schema, so the description must carry the return-value burden, and it does list the main reported signals. The exact response shape and behavior for a nonexistent agent_id remain unspecified, but the gaps are minor for a tool of this complexity.

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 parameters are already documented in the schema. The description reinforces the 'one agent vs entire pool' scoping but adds no syntax, format, or interaction detail beyond what the schema provides, making the baseline 3 appropriate.

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 ('status inspection') and resource ('one agent or the entire Antigravity subagent pool'), plus the fields returned (active count, queue length, step progress, circuit-breaker cooldown). It is clearly distinguishable once read, though it never names a sibling such as agy_wait_agent or agy_health to draw the boundary explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'non-blocking' implies the key selection condition versus a blocking wait, and the schema-level note says to omit agent_id to list all. But the description itself gives no explicit when-to-use/when-not-to-use guidance and does not route the agent to an alternative tool.

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