Skip to main content
Glama

agy_health

Read-only

Check Antigravity CLI readiness, proxy settings, model IDs, and pool concurrency status without using model quota; optionally refresh cached model output.

Instructions

Check Antigravity CLI readiness, proxy configuration, available model IDs, and current concurrency/cooldown pool status without consuming model quota.

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_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
refresh_modelsNoForce-refresh cached `agy models` output.

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?

The annotations declare readOnlyHint=true, and the description reinforces that with a concrete behavioral guarantee — no model quota is consumed — which is valuable context beyond the annotation. It also implies caching via the mention of 'available model IDs' and the refresh flag, though it does not describe the shape of the report or how failures surface.

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?

One dense sentence with zero filler, front-loading the verb and the full set of checked surfaces, then closing with the differentiating constraint (no quota consumption). Nothing is repeated from the title or schema.

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?

For a read-only diagnostic with one optional flag, no output schema, and full schema coverage, the description covers what is inspected and the cost profile. The remaining gap is how the results are presented and how it relates to agy_status, but 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 optional parameter (refresh_models) is fully documented in the schema, including its default and the fact that it force-refreshes cached `agy models` output. The description adds no syntax or behavioral detail about the flag, so the baseline 3 applies.

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?

The description uses a specific verb ('Check') and enumerates exactly what is inspected: CLI readiness, proxy configuration, model IDs, and concurrency/cooldown pool status. It is unambiguous about scope, though it does not differentiate itself from the sibling agy_status, which by name appears to cover overlapping status-reporting ground.

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?

Usage is only implied: the phrase 'without consuming model quota' hints that this is a cheap preflight/diagnostic call, and the name plus 'readiness' suggests checking before spawning agents. There is no explicit statement of when to use this versus agy_status, nor any exclusions or prerequisites.

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