Skip to main content
Glama

survey

Maps Codex or Antigravity app interfaces by opening pages and menus, returning a summary and diff from the previous map with missing landmarks flagged.

Instructions

Map the interface of Codex or Antigravity now (otherwise done automatically when its version changes): pages and menus opened, read and closed with Escape, never an action; refused while the user is in the app; view restored. Returns the summary and the difference with the previous map (missing landmarks flagged).

Args: app: "codex" or "antigravity".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "survey"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.7
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "surveyOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that pages and menus are opened, read, and closed with Escape, that no action is taken, that the view is restored, and that calls are refused while the user is in the app. It also states the return value: a summary and difference from the previous map.

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?

The purpose and constraints are front-loaded, and the Args section is brief. The parenthetical and run-on phrasing in the first sentence are slightly awkward but not wasteful.

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

Completeness5/5

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

For a one-parameter tool with no output schema, the description covers what it does, when it runs, safety/refusal behavior, view restoration, and return contents. Nothing material needed to invoke it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema merely declares a string parameter. The description supplies the only useful semantic detail: app must be either "codex" or "antigravity", effectively providing the missing enum.

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?

The description states a specific verb and resource: map the interface of Codex or Antigravity. It is clear enough to distinguish from CRUD-style siblings, though it does not explicitly name or contrast with any sibling tool.

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?

It explains that the survey can be run now, that it is otherwise automatic when the app version changes, and that it is refused while the user is in the app. That gives clear context and a usage constraint, though it does not compare alternatives.

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