Skip to main content
Glama
PyModel

claude-agy-mcp

by PyModel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

web_lookup

Look up library docs, API references, error messages, and current versions on the web when the answer is missing from or newer than your training data.

Instructions

Delegate a web/documentation lookup to the Antigravity CLI (Gemini with web access): library docs, API references, error messages, current versions, external knowledge. USE THIS when you need information you don't have or that may be newer than your training data.

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 look up on the web.
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.6/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 burden. It does disclose the delegation mechanism (an external Antigravity CLI backed by Gemini with web access), which is useful behavioral context, but says nothing about latency, cost, failure modes, or that the call spawns a separate agent process. For a delegated external call with zero annotation coverage, that is a notable gap.

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 sentences, no filler; the purpose comes first and the invocation trigger is front-loaded with a capitalized cue. Terse relative to a seven-parameter tool, but nothing in it is wasted.

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

Completeness3/5

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

For a delegation tool with no output schema and no annotations, the description should say what comes back (a text answer, optionally structuredContent) and what a call costs in time. The schema hints at structured output and latency for one parameter only; the description leaves return shape and latency expectations unaddressed.

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 query, cwd, dirs, model, effort, schema, and slash_commands in detail (including the cost warning on schema and the security note on slash_commands). The description adds nothing further about parameters, 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 concrete verb and resource — delegating a web/documentation lookup to an external CLI agent with web access — and enumerates the kinds of questions it answers (library docs, API references, error messages, versions). It never names a sibling, so it misses explicit differentiation from deep_search or the generic delegate tools, but the purpose itself is unambiguous.

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?

The second sentence gives a real trigger condition: use it when you lack information or the information may postdate your training data. That is clear, actionable routing logic. It stops short of stating when NOT to use it or pointing to deep_search/delegate as the alternative for non-web lookups.

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