Skip to main content
Glama

Antigravity status

agy_status

Reports the current version, signed-in account, active configuration, and live conversations managed by this server so you can verify agent state.

Instructions

Report agy version, the signed-in account, configuration in effect, and the live conversations managed by this server.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Report' implies a non-mutating read, and the description usefully discloses what is surfaced — notably that it reveals the signed-in account, which has privacy implications. However, it says nothing about failure behavior, whether the status call can trigger side effects, or how 'live conversations managed by this server' relates to the agy_conversations sibling.

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 sentence that front-loads the verb and lists the four reported items without filler. Every clause earns its place.

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 no output schema, the description steps in to enumerate the returned fields (version, account, config, conversations), which is exactly what an agent needs. The only gap is the absence of any read-only/safety statement, which matters because no annotations are provided.

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, which is the baseline-4 case. The description correctly reflects a no-argument invocation, and there is nothing for it to clarify further.

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 gives a specific verb ('Report') and enumerates four concrete resources: version, signed-in account, effective configuration, and live conversations. This is clearly distinct from agy_ask/agy_stop (action tools), though the 'live conversations' element overlaps somewhat with the sibling agy_conversations, and no explicit differentiation is drawn.

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: a status/diagnostic check before or after using the other agy_* tools. There is no explicit statement of when to prefer this over agy_conversations or agy_models, and no exclusions are given.

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