Skip to main content
Glama
Sign In
Cat Burglar

Cat Burglar

by DrMkdaddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Snapshot page

snapshot
Read-only

Capture a compact view of the current page with stable element refs, control states, and visible text, then retrieve only changes since a prior observation to track updates and act reliably.

Instructions

Compact view of the current page: URL, title, actionable elements with refs (e1, e2…), control states, and visible text. Refs stay stable while the element remains in the DOM; a new snapshot does not renumber them. Use diff=true (or since=sN) to see only changes since the last observation. Prefer refs over CSS selectors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffNoReturn only changes since the previous snapshot. Profile default applies.
sinceNoDiff against a specific snapshot id (e.g. s4) instead of the latest.
max_charsNoCharacter budget (profile default). Controls get priority over body text.
include_textNoInclude visible body text (default true).
max_controlsNoMax controls (profile default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes safety, so the description's added value is elsewhere: it guarantees that refs stay stable while the element remains in the DOM and are not renumbered by a new snapshot. That is a meaningful behavioral contract for an agent that caches refs between calls. It does not discuss truncation behavior or how max_chars interacts with the output, which keeps it below 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?

The output shape is front-loaded in the first sentence, followed by the ref-stability contract, the diffing shortcut, and a final usage preference. Every sentence carries information an agent needs, and there is no redundant framing.

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?

With no output schema, the description carries the burden of describing the return payload, and it does so concisely (URL, title, elements with refs, control states, visible text). Combined with the readOnlyHint annotation and fully documented schema, an agent has everything needed to call this 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 five parameters, establishing a baseline of 3. The description adds some relational meaning by presenting since=sN as an alternative to diff=true and tying ref stability to reuse across snapshots, but it does not explain formats or priority rules beyond what the schema states.

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 exactly what the tool returns: URL, title, actionable elements with refs (e1, e2…), control states, and visible text. It is far more specific than the title 'Snapshot page' and implies its role relative to selector-based approaches. It does not explicitly distinguish itself from siblings like markdown, extract, or screenshot, keeping it at a 4.

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 gives concrete usage guidance: use diff=true or since=sN to see only changes, and prefer refs over CSS selectors when driving other tools. This tells the agent how to use the tool across observation cycles. It does not say when not to use it or name an explicit alternative tool, so it falls short of a 5.

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