Skip to main content
Glama

health

Read-onlyIdempotent

Verify Antigravity CLI setup, authentication, available models, and session status; enable verbose diagnostics or target a session ID for troubleshooting.

Instructions

Check Antigravity CLI installation, authentication, available models, and session health

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": "health"
  }
}

Input Schema

NameRequiredDescriptionDefault
verboseNoInclude detailed diagnostic information
sessionIdNoOptional session ID to check specific session health

Output Schema

NameRequiredDescriptionDefault
agyCliYes
issuesYes
statusYes
sessionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and side-effect profile are covered structurally. The description adds the substantive detail that this touches installation, auth, and models, implying real environment/network probing. It does not disclose cost, latency, whether checks can fail partially, or what a degraded result means, which matters for a health probe.

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?

A single front-loaded sentence with no filler, and the checklist structure makes the scope immediately scannable. It is slightly clipped as a fragment and does not lead with an action cue, but nothing is wasted.

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 annotations, a complete input schema, and an output schema already present, the description only needs to convey scope, which it does explicitly. The remaining gap — how this differs from the overlapping diagnostic siblings — is modest for a tool whose return shape is already documented.

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% with both parameters fully documented, so the schema carries the explanatory load. The description only obliquely gestures at sessionId via 'session health' and says nothing about verbose, so baseline 3 is 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?

Names a specific verb ('Check') and enumerates concrete resources: CLI installation, authentication, models, and session health. An agent knows exactly what it probes. It does not, however, distinguish itself from siblings that clearly overlap (list-models, list-sessions, ping, version), so it falls short of a 5.

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 diagnostic framing implies a pre-flight or troubleshooting use, but nothing is stated about when to call this versus ping, version, or list-models, nor any when-not condition. Usage is inferable from the name and the enumerated checks rather than explicitly guided.

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