Skip to main content
Glama

agy bridge diagnostics

antigravity_status
Read-onlyIdempotent

Check Antigravity setup, version, per-model quota, state directories, and bridge health to debug empty or failed answers before spending quota.

Instructions

Check the agy (Antigravity) setup. Spends no quota; run it first when a call says "not found". Its bridge version row says when a newer agent-intern release is out: if so, tell the user. Also checks agy's version, the AI Pro quota left per model family (a family at 0% fails every call until it resets), agy's state directories, and whether the bridge can still read agy's answers. Use it to debug empty or failed answers before spending 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": "antigravity_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnly/idempotent/closed-world; the description adds genuinely new behavior: zero quota cost, that a model family at 0% fails every call until reset, that the bridge version row indicates whether a newer agent-intern release exists, and an instruction to tell the user when it does. It stops short of describing the output shape, but an output schema exists, so that omission is acceptable.

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?

Front-loads the core action and the no-quota reassurance, then lists the individual checks. Slightly long and the parenthetical '(Antigravity)' plus the embedded release-note instruction add density, but every clause carries operational information.

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?

For a zero-parameter diagnostic with an output schema already covering return values, the description supplies everything needed: what is checked, what each notable result means (0% quota family, newer bridge release), the safety profile (no quota spent), and when to invoke it relative to failing calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly adds no param detail, which is appropriate here.

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 ('Check the agy (Antigravity) setup') and then enumerates the concrete checks: bridge version, agy version, AI Pro quota per model family, state directories, and answer-reading capability. That enumeration distinguishes it cleanly from the ask/continue siblings and from the other *_status tools, which cover different providers.

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?

Gives explicit trigger conditions: run it first when a call returns 'not found', and use it to debug empty or failed answers before spending quota. It also signals the cost tradeoff ('Spends no quota'), which tells the agent why this should precede the quota-consuming siblings.

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