Skip to main content
Glama
Sign In
Pinpoint

Pinpoint

by gowtham012
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Re-check an annotation against the live page

recheck_annotation

Verify a marked browser element before editing stale annotations: locate it again, report changes, and return a fresh crop.

Instructions

Ask the developer's browser to find this element again, right now, and report what changed since they marked it — with a fresh crop next to the original one. Call it before editing anything marked a while ago, and whenever an annotation says it may be stale. A verdict of gone or moved means the selector in the annotation should not be trusted as-is.

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": {
      "id": "<id>"
    },
    "name": "recheck_annotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAnnotation id (8 chars) or its pin number
timeoutSecondsNoHow long to wait for the browser. Default 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations to lean on, the description carries the load and does so fairly well: it discloses that this reaches into the developer's live browser right now, that it returns a diff plus a fresh crop relative to the original capture, and the meaning of gone/moved verdicts. It omits latency/timeout expectations and any failure modes beyond the verdict vocabulary.

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 short sentences, each doing a distinct job: the action and its output, the trigger conditions, and how to interpret the verdict. The scope constraint and the payoff are front-loaded; nothing is padding.

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?

There is no output schema, so the description must cover return semantics — and it does, naming the diff, the fresh crop, and the gone/moved verdicts. Combined with the fully documented parameters, an agent has everything needed to call and interpret this tool.

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 both parameters (id, timeoutSeconds) are already documented with format and defaults. The description only implies the id targets an element and adds nothing about the timeout or id format, so the baseline 3 applies.

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 — re-verify an annotation's element against the live page and report the diff — with a concrete output artifact (a fresh crop alongside the original). It is clearly distinct from siblings like get_annotation or resolve_annotation, which fetch or close annotations rather than re-validating them.

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?

Gives two explicit triggers: call before editing anything marked a while ago, and whenever an annotation flags itself as possibly stale. It also explains how to act on the verdict (gone/moved means the selector can't be trusted as-is), but never states when not to call it or which sibling to prefer for adjacent needs.

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