Skip to main content
Glama

agy_status

Read-onlyIdempotent

Inspect system health, Gemini quota windows, local GPU VRAM, job queue state, and session token savings in read-only mode. Check worker or model tier status before routing work.

Instructions

Inspect current system health, Gemini 5-hour/weekly quota windows, Local GPU VRAM availability (/api/ps), process queue state (active_job, waiting_jobs, recent_jobs with job_id, state, started_at, elapsed_s, tier, prompt_preview), active session context remaining, and Git worktree pre-flight status in read-only mode. WHEN TO USE: Checking whether the Local GPU worker or Gemini Argon/Flash tiers are online, inspecting in-flight/queued jobs, and checking token savings. DO NOT USE FOR: Modifying workspace settings or attaching the IDE (use agy_configure_workspace instead). RETURNS: JSON status report { agy_process_queue, local_gpu_queue, local_gpu_probe, local_gpu_telemetry, model_quotas, sessions } plus telemetry footer.

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
refresh_modelsNoIf true, runs `agy models` to probe for newly released Gemini models (defaults to false for instant response).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / refresh_models / default
      Added value: +false
    • changedInput schema / properties / refresh_models / description
      Previous value: -"If true, runs `agy models` to check for newly released Gemini models."New value: +"If true, runs `agy models` to probe for newly released Gemini models (defaults to false for instant response)."
    • addedInput schema / required
      Added value: +[]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description reinforces read-only mode while adding genuinely new context: which subsystems are probed, the `/api/ps` endpoint, and the exact shape of the returned status report including telemetry footer. It does not mention latency behavior for the refresh path (only the schema does) or failure modes, so it falls just short of a 5.

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?

Well front-loaded and organized into WHEN TO USE / DO NOT USE FOR / RETURNS blocks, which makes scanning easy. The parenthetical enumeration of job fields (`job_id`, `state`, `started_at`, `elapsed_s`, `tier`, `prompt_preview`) is dense and partly redundant with the RETURNS key list, adding bulk without much selection value.

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?

A zero-required-parameter read-only inspection tool with no output schema, yet the description supplies the return object's top-level keys and mentions the telemetry footer, so the agent knows what it will get back. Nothing needed to invoke it correctly is missing.

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% and the single `refresh_models` parameter is fully documented in the schema with its default and the `agy models` probing behavior. The description says nothing about the parameter, so baseline 3 applies – no added value, but no burden either since the schema carries it.

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?

Opens with a specific verb ('Inspect') and enumerates exactly what is inspected: system health, Gemini quota windows, Local GPU VRAM via `/api/ps`, process queue state, session context, and Git worktree status. Sibling differentiation is explicit in the DO NOT USE clause pointing at agy_configure_workspace.

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?

Dedicated WHEN TO USE section covers the three main situations (checking worker/tier availability, inspecting in-flight and queued jobs, checking token savings), and DO NOT USE FOR names the concrete alternative for the excluded case. An agent can route correctly without opening any schema.

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