Skip to main content
Glama

where

Read-onlyIdempotent

Locate buttons and menus in Codex or Antigravity by reading a stored interface map, returning paths, landmarks, attributes, and gestures without navigating.

Instructions

Where a button or menu is in Codex or Antigravity, from the latest map of its interface: path (page, menu, submenu), relay landmark (NEW_CHAT, ARCHIVE, MODE, CHAT_ACTIONS...), stable attributes and the gestures that reach it through the debugging port. No navigation: only the stored map is read.

Args: app: "codex" or "antigravity". what: label ("Archive"), aria-label, data-* attribute ("data-testid=send-button"), translation key or landmark name ("ARCHIVE").

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>",
      "what": "<what>"
    },
    "name": "where"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
whatYes

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": "whereOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new context: it reads a stored map and does NOT navigate, and it discloses what the response contains. This goes beyond the annotation set without contradicting it.

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 lead sentence is front-loaded and information-dense, and the Args block adds real meaning rather than restating types. Slightly verbose line-wrapping but no wasted content.

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?

With no output schema, the description helpfully enumerates the return shape and clarifies the non-navigating behavior. It is nearly complete for a two-parameter read-only lookup; only explicit sibling routing is missing.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the load, and it does: 'app' enumerates the two valid values and 'what' lists accepted formats with concrete examples (label, aria-label, data-* attribute, translation key, landmark). This compensates well, though format-vs-string ambiguity could be spelled out further.

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 ('where... is') and resource (button/menu in Codex or Antigravity) and enumerates the return payload (path, relay landmark, stable attributes, gestures). It is distinguishable from siblings like send/status, though it never names a sibling to contrast against.

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

Usage Guidelines3/5

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

The closing note 'No navigation: only the stored map is read' implies this is a lookup rather than an action, which nudges usage, but there is no explicit when-to-use or when-not-to-use guidance relative to siblings such as send or status.

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