Skip to main content
Glama
PyModel

claude-agy-mcp

by PyModel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_files

Delegate file analysis of large files, logs, or multi-file reviews to the Antigravity CLI (Gemini) so files never enter context—only the answer returns.

Instructions

Delegate file analysis to the Antigravity CLI (Gemini) instead of reading files yourself. USE THIS whenever a file is large (>200 lines) or the task spans more than 3 files: logs, database dumps, generated code, cross-file reviews, comparisons. The files never enter your context — only the answer does.

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.
filesYesFile paths to analyze (relative to cwd or absolute).
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.
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.
questionYesWhat you want to know about these files.
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. Changed9 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 / files / items / minLength
      Added value: +1
    • addedInput schema / properties / files / 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 / question / 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

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden, and it does the most important part well: it names the context-isolation behavior ('files never enter your context — only the answer does'), which is the key mental model for a delegation tool. It does not state the safety profile (read-only vs. workspace-mutating), latency, or the prompt-injection hazard that is only mentioned inside the slash_commands parameter description, so it stops short of full behavioral disclosure.

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 sentences, all load-bearing: purpose/mechanism first, then the trigger conditions, then the context-cost payoff. No filler and the most decision-relevant information is front-loaded.

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 an 8-parameter tool with full schema coverage and no output schema, the description covers purpose, triggers, and the return-value shape ('only the answer does'), which is enough to call it correctly. It leaves the security-relevant slash_commands caveat stranded in the parameter description and never states whether analysis is strictly read-only, which are minor but real gaps.

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% across all 8 parameters, so cwd, dirs, model, effort, schema, and slash_commands are already documented in the schema. The description adds only implicit guidance about the files parameter (large files, multi-file scope) and nothing about the rest; baseline 3 is correct when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (delegate file analysis) plus the mechanism (Antigravity CLI / Gemini), and explicitly contrasts itself with the default behavior of reading files directly. An agent can tell this apart from generic delegation or web/search siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit, testable triggers — '>200 lines' or '>3 files' — plus concrete task categories (logs, database dumps, generated code, cross-file reviews, comparisons). This is exactly the when-to-use guidance that lets an agent route between this and reading files itself.

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