Skip to main content
Glama
Sign In
Mochi

Mochi

by DevZonayed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_snapshot_node

Retrieve a compact subtree from a stored browser snapshot using a reference, text, or path for targeted drilldown.

Instructions

Return a compact subtree from the latest stored browser_snapshot by ref, text, or path from browser_snapshot_query. Use for targeted drilldown.

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

Input Schema

NameRequiredDescriptionDefault
snapshotIdNoDefaults to the latest stored snapshot.
refNoExact ref/selector to return.
textNoFirst node whose name/text/descendant text contains this value.
pathNoDot-separated child path returned by browser_snapshot_query, e.g. '0.3.1'.
maxDepthNo
maxBytesNo
redactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states that the default snapshotId uses the latest stored snapshot but does not disclose side effects, return format, or constraints (e.g., maxDepth, maxBytes, redact 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?

The description is two concise sentences with no extraneous information. It front-loads the core action and usage context efficiently.

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

Completeness2/5

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

Given 7 parameters, no output schema, and no annotations, the description is too brief. It lacks explanation of parameters like maxDepth, maxBytes, and redact, and does not describe the output format. It relies heavily on schema descriptions that have low coverage.

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

Parameters2/5

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

Schema description coverage is 57% (low), yet the description adds minimal meaning beyond listing the selection methods. It does not explain parameter interactions or provide examples. The schema descriptions already cover many parameters, so the description's contribution is limited.

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?

The description clearly states the tool returns a compact subtree from a browser_snapshot and specifies the selection methods (ref, text, or path). It distinguishes from sibling tools like browser_snapshot (full snapshot) and browser_snapshot_query (query).

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 description says 'Use for targeted drilldown,' implying a specific use case. However, it does not explicitly state when not to use it or provide alternatives beyond the implicit context of sibling tool names.

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