Skip to main content
Glama
rhishi99

agy-headless-bridge MCP server

by rhishi99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agy_ask

Delegate a focused coding, debugging, or reasoning task to Gemini through the Google Antigravity CLI and return its one-shot response.

Instructions

Send a one-shot prompt to the Google Antigravity CLI (agy) and return its response. Use to delegate a focused coding, debugging, or reasoning task to Gemini via Antigravity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoagy --model (optional)
promptYesThe prompt to send to agy
add_dirNoExplicit directories to add to agy's workspace. Overrides the workspace default below.
timeoutNoHard timeout in seconds (override when a task legitimately needs longer).
workspaceNoauto (default): if no add_dir given, add the server's cwd so agy sees the repo — needed for coding tasks. none: no workspace (use for research / Q&A that needs no repo context).
skip_permissionsNoLet agy edit files / run commands without approval prompts (headless agy otherwise declines them silently). Only honoured if the server was started with AGY_BRIDGE_ALLOW_SKIP_PERMISSIONS=1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / properties / skip_permissions
      Added value: +{
+  "description": "Let agy edit files / run commands without approval prompts (headless agy otherwise declines them silently). Only honoured if the server was started with AGY_BRIDGE_ALLOW_SKIP_PERMISSIONS=1.",
+  "type": "boolean"
+}
  2. Changed4 schema fields changedv1.2.0
    • addedInput schema / properties / add_dir
      Added value: +{
+  "description": "Explicit directories to add to agy's workspace. Overrides the workspace default below.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / model
      Added value: +{
+  "description": "agy --model (optional)",
+  "type": "string"
+}
    • addedInput schema / properties / timeout
      Added value: +{
+  "description": "Hard timeout in seconds (override when a task legitimately needs longer).",
+  "type": "number"
+}
    • addedInput schema / properties / workspace
      Added value: +{
+  "description": "auto (default): if no add_dir given, add the server's cwd so agy sees the repo — needed for coding tasks. none: no workspace (use for research / Q&A that needs no repo context).",
+  "enum": [
+    "auto",
+    "none"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioural burden. It conveys 'one-shot' (single turn) and that a response is returned, but omits that agy can edit files and run commands (the skip_permissions param implies a mutation-capable, headless agent), credential/auth requirements, and timeout/long-task behaviour. These side-effect risks are material and unstated in the description.

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?

Two tight sentences, front-loaded with the action, zero filler. It could still be marginally more informative without bloating, so not a top mark.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, mutation-capable CLI bridge with no annotations and no output schema, the description is thin: it says nothing about file-editing side effects, permission/skip gating, or result shape. An agent could call it correctly on arguments but would misjudge its blast radius.

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 description coverage is 100%, so the schema already documents model, prompt, add_dir, timeout, workspace and skip_permissions in detail. The description adds no parameter-level syntax or defaults beyond what the schema provides, making the baseline 3 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?

States a concrete verb and resource: send a one-shot prompt to the Antigravity CLI (agy) and return its response. This clearly separates it from a stateful/session tool, and the delegation scoping (coding, debugging, reasoning) hints at its niche versus agy_research without naming the sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear use context: delegate a focused coding, debugging, or reasoning task to Gemini. It stops short of an explicit when-not-to-use rule or naming agy_research as the alternative for research/Q&A, so routing between the two siblings is left partly to inference.

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