Skip to main content
Glama
Sign In
Free Codin Agent

Free Codin Agent

by office233
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

chrome_snapshot

Read-onlyIdempotent

Capture a semantic snapshot of a Chrome tab to list interactive elements with [#N] refs and page-declared tools before clicking or typing.

Instructions

Semantic snapshot of a tab: interactive elements with [#N] refs, plus page-declared site tools. Take one before clicking or typing.

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": "chrome_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoChrome tab id (default: active tab)
frameIdNoFrame id, default 0
snapshotIdNosnapshotId returned by chrome_snapshot; rejects stale actions
maxElementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare it as read-only, idempotent, non-destructive, and open-world. The description adds valuable behavioral context about the snapshot's content format and the required ordering before interaction actions, though it does not mention rate limits or pagination behavior.

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?

Two tightly written sentences with zero waste. The output format is front-loaded, followed immediately by the action-oriented usage instruction.

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 usefully summarizes the return shape (interactive elements with refs, site tools) and pairs it with the required workflow. It omits details about maxElements, frameId behavior, and what 'site tools' entail, but is sufficient for correct tool selection and basic invocation.

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 75%, so most parameters are documented in the schema. The description adds no parameter-specific semantics beyond the general output format, so a baseline 3 is appropriate.

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 specific verb and resource ('snapshot of a tab') and specifies the output content ('interactive elements with [#N] refs, plus page-declared site tools'). It distinguishes a semantic snapshot from a visual screenshot implicitly, but does not explicitly contrast it with siblings like chrome_screenshot or browser_snapshot.

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 clear usage context: 'Take one before clicking or typing.' This tells the agent when to call it, but does not state when to avoid it or name an alternative tool.

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