claude-agy-mcp

Overview Schema Source Related Servers Discussions Admin

delegate

Delegate complex tasks to the Antigravity CLI when other tools fall short. Runs read-only by default; enable write or sandbox modes as needed.

Instructions

Raw delegation to the Antigravity CLI for heavy tasks that don't fit the other tools. Read-only by default; pass write: true to let agy edit files, sandbox: true to confine it. Anything it was refused comes back as a denied-actions note.

Input Schema

TableJSON Schema

Name	Required	Description
`cwd`	No	Absolute path to the working directory / project root. Defaults to the server's cwd.
`dirs`	No	Extra directories to add to agy's workspace, for cross-repo or worktree-vs-base analysis.
`model`	No	Override the model. Accepts a display name ("Gemini 3.8 Flash (High)"), an id ("gemini-3.8-flash-high"), or a family selector ("gemini-pro@latest-high"). Normally omit — the tool routes automatically.
`write`	No	Allow file edits and command execution. Off by default.
`effort`	No	Reasoning tier. Gemini models carry their tier in the name, so this switches to the sibling model at that tier (Flash (High) -> Flash (Medium)); agy's own --effort flag only reaches models without a tier. Defaults to the user's set_model choice, else the tool's own tier.
`prompt`	Yes	The complete task prompt for agy.
`schema`	No	JSON Schema (as a string) constraining the answer. Returns structuredContent as well as text. Costs noticeably more latency and tokens, so use it only when you will parse the result.
`sandbox`	No	Run agy with terminal restrictions enabled.
`slash_commands`	No	Let agy expand your slash commands and skills into the prompt. Off by default: a hostile file in the workspace can otherwise steer the delegated model.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv3.1.0Sep 13, 2026
- addedInput schema / properties / cwd / minLength
```
Added value: +1
```
- addedInput schema / properties / dirs / items / minLength
```
Added value: +1
```
- addedInput schema / properties / dirs / maxItems
```
Added value: +256
```
- addedInput schema / properties / model / maxLength
```
Added value: +512
```
- addedInput schema / properties / model / minLength
```
Added value: +1
```
- addedInput schema / properties / model / pattern
```
Added value: +"^[^-]"
```
- addedInput schema / properties / prompt / pattern
```
Added value: +"\\S"
```

Changed7 schema fields changedv2.1.0Sep 12, 2026

addedInput schema / properties / dirs

Added value: +{
+  "description": "Extra directories to add to agy's workspace, for cross-repo or worktree-vs-base analysis.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / effort

Added value: +{
+  "description": "Reasoning tier. Gemini models carry their tier in the name, so this switches to the sibling model at that tier (Flash (High) -> Flash (Medium)); agy's own --effort flag only reaches models without a tier. Defaults to the user's set_model choice, else the tool's own tier.",
+  "enum": [
+    "low",
+    "medium",
+    "high"
+  ],
+  "type": "string"
+}

changedInput schema / properties / model / description

Previous value: -"Override the model (exact name from `agy models`, e.g. \"Gemini 3.1 Pro (High)\"). Normally omit — the tool routes automatically."New value: +"Override the model. Accepts a display name (\"Gemini 3.8 Flash (High)\"), an id (\"gemini-3.8-flash-high\"), or a family selector (\"gemini-pro@latest-high\"). Normally omit — the tool routes automatically."

addedInput schema / properties / sandbox

Added value: +{
+  "description": "Run agy with terminal restrictions enabled.",
+  "type": "boolean"
+}

addedInput schema / properties / schema

Added value: +{
+  "description": "JSON Schema (as a string) constraining the answer. Returns structuredContent as well as text. Costs noticeably more latency and tokens, so use it only when you will parse the result.",
+  "type": "string"
+}

addedInput schema / properties / slash_commands

Added value: +{
+  "description": "Let agy expand your slash commands and skills into the prompt. Off by default: a hostile file in the workspace can otherwise steer the delegated model.",
+  "type": "boolean"
+}

addedInput schema / properties / write

Added value: +{
+  "description": "Allow file edits and command execution. Off by default.",
+  "type": "boolean"
+}

Changed1 schema field changedv2.0.0Aug 19, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.0Aug 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the read-only default, that write:true permits file edits and command execution, that sandbox:true confines execution, and that refused actions surface as a denied-actions note. It omits auth/permission prerequisites and latency expectations beyond what the schema already notes.

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, purpose front-loaded, then safety defaults, then the denial behavior. Every clause earns its place with no redundancy.

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 nine-parameter delegation tool with no output schema, the description covers the safety-relevant behavior and the one notable return artifact (denied-actions note). It stops short of describing the normal success return shape, but the rich schema compensates for the parameter side.

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 all nine parameters in detail. The description restates the write and sandbox semantics but adds no format, default, or interaction detail beyond what the schema provides; baseline 3 applies.

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 and target resource: raw delegation to the Antigravity CLI for heavy tasks. It gestures at sibling differentiation ('tasks that don't fit the other tools') but never names the sibling (e.g. delegate_many or deep_search) that would be preferred, so an agent can't fully route on this alone.

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?

Gives implied context ('heavy tasks that don't fit the other tools') but no explicit when-to-use/when-not or named alternatives. The agent must infer from the sibling list whether this or delegate_many/deep_search is appropriate.

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

Deploy Server

delegate

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools