Skip to main content
Glama
Sign In
antigravity-plugin-codex

antigravity-plugin-codex

by irrumi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

antigravity_doctor

Inspect installed agent CLI version and help. Optionally probe authentication with a real prompt; never infer auth from config directories.

Instructions

Inspect installed agent CLI/version/help. probeAuth sends a small real prompt and may incur usage. Never infer auth from config directories.

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

Input Schema

NameRequiredDescriptionDefault
probeAuthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden, and it delivers two meaningful traits: probeAuth performs a real call that 'may incur usage' (a cost/side-effect warning), and the explicit anti-pattern 'Never infer auth from config directories'. It still omits whether the inspection itself is read-only or what it returns, so it is not fully complete.

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?

Three tight sentences with zero filler; the primary purpose is front-loaded, followed by the parameter cost caveat and the methodology warning in priority order.

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 one-parameter diagnostic tool with no output schema, the description covers what it does and the main behavioral risk. It could add whether the command is non-destructive and roughly what it reports, but nothing critical to correct invocation is missing.

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?

Schema coverage is 0%, so the description must explain the single parameter, and it does: probeAuth 'sends a small real prompt and may incur usage'. That conveys the semantics and the cost implication the bare boolean type could not. Minor gap: no mention of the default when omitted.

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?

States a specific verb (Inspect) and resource (installed agent CLI/version/help), which is a diagnostic intent clearly distinct from the ask/delegate/review/status siblings. It does not explicitly name an alternative, so it falls short of the 5 bar.

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 implied (run this to inspect the installed CLI) but there is no explicit when-to-use/when-not framing or named sibling for comparison. The probeAuth caveat gives conditional guidance for that parameter, not for choosing the tool.

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

Deploy Server

Other Tools