Skip to main content
Glama
PyModel

claude-agy-mcp

by PyModel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

adversarial_review

Get an adversarial second opinion from Gemini Pro to review plans, designs, and pre-merge code, finding flaws, edge cases, security issues, and unstated assumptions.

Instructions

Get an adversarial second opinion from a different model family (Gemini Pro). ALWAYS use this for plan critiques, design reviews, and pre-merge code review: it hunts for flaws, edge cases, security issues, and unstated assumptions you may have missed. Pass either content or files — a call with neither is rejected. Pass schema to get ranked findings back as data instead of prose.

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.
filesNoFile paths to review instead of inline content.
focusNoOptional focus area, e.g. 'security', 'concurrency'.
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.
contentNoInline content to review (plan, diff, code snippet).
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. Changed8 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: +"^[^-]"
  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?

No annotations are provided, so the description carries full burden and does well: it discloses the model family used, the specific behavior (hunts for flaws, edge cases, security issues, unstated assumptions), and the call-rejection rule for empty input. It doesn't cover cost/rate limits beyond the `schema` latency-and-token note, or what happens to files read from disk, keeping it from a 5.

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, each earning its place: identity, when-to-use with rationale, and the input/return contract. Front-loaded with the 'what it is' before the usage rule.

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 9-param tool with no annotations and no output schema, the description covers purpose, usage rule, input constraint, and the optional structured-output path. Missing details are minor (return shape when no schema is passed, cost/working-directory behavior), but an agent could call it correctly.

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 9 parameters in detail (cwd, dirs, files, focus, model, effort, schema, content, slash_commands). The description adds only the `content`-or-`files` mutual-requirement and the `schema` structured-output behavior, which is useful but marginal against the schema's own documentation. Baseline 3 is correct.

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?

Specific verb + resource ('adversarial second opinion from a different model family (Gemini Pro)') and it explicitly distinguishes itself from sibling delegation tools by naming the critique/review use case (plan critiques, design reviews, pre-merge code review). An agent can tell this apart from `delegate` or `delegate_many` without opening schemas.

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?

States 'ALWAYS use this for plan critiques, design reviews, and pre-merge code review' — an explicit when-to-use directive — and adds the input constraint 'Pass either `content` or `files` — a call with neither is rejected.' Clear routing plus an exclusion/precondition.

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