Skip to main content
Glama
PyModel

claude-agy-mcp

by PyModel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

deep_search

Answer codebase history and usage questions by delegating git log, diff, blame, and wide greps to the Antigravity CLI, saving your context instead of running many searches yourself.

Instructions

Delegate codebase archaeology to the Antigravity CLI: git log/diff/blame spelunking, wide greps across a repo, 'when/why did X change', 'where is Y used'. USE THIS instead of running many search commands yourself — it saves your context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoAbsolute path to the working directory / project root. Defaults to the server's cwd.
dirsNoExtra directories to add to agy's workspace, for cross-repo or worktree-vs-base analysis.
modelNoOverride 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.
queryYesWhat to find, e.g. 'when was the auth middleware refactored and why'.
effortNoReasoning 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.
schemaNoJSON 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.
slash_commandsNoLet 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.

  1. Changed7 schema fields changedv3.1.0
    • 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 / query / pattern
      Added value: +"\\S"
  2. Changed5 schema fields changedv2.1.0
    • 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 / 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"
+}
  3. Changed1 schema field changedv2.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that work is delegated to an external CLI and that this preserves the caller's context, which is genuinely useful, but it says nothing about latency, token cost, or that results come back as text (the schema mentions structuredContent only under 'schema'). Key trade-offs are left to the parameter docs.

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?

Two sentences, the capability and its examples front-loaded, and the differentiator ('instead of running many search commands yourself') placed last as the call-to-action. No filler sentences.

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 seven-parameter delegation tool with no output schema, the description plus the fully covered schema gives an agent enough to call it correctly. What is missing is call-level behavior: expected latency, cost, and whether output is text or structured by default.

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 every one of the seven parameters is already documented in the schema with rich detail (model routing, effort tier interaction, structured-output cost, slash_commands security). The description adds no parameter-level meaning beyond that, so the 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+resource (delegate codebase archaeology to the Antigravity CLI) and enumerates the concrete operations it covers: git log/diff/blame, wide greps, 'when/why did X change'. The scope is crisp enough to separate it from a generic delegate call, though no sibling tool (delegate, analyze_files, delegate_many) is named to sharpen the boundary.

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?

'USE THIS instead of running many search commands yourself — it saves your context' gives an explicit when-to-use and an implicit when-not (don't hand-roll many search commands). It lacks any pointer to sibling alternatives for non-search delegation, so the routing guidance is clear but not complete.

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