Skip to main content
Glama
Sign In
witness

witness

by wookat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_dom_state

Fetch the DOM snapshot HTML nearest a given timeline millisecond, returning its path and HTML to inspect the page state at that moment.

Instructions

DOM snapshot HTML nearest to a timeline ms (snapshots at nav/mark/every 30s). Returns path + html

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": {
      "t_ms": "<t_ms>"
    },
    "name": "get_dom_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
t_msYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add two real facts: results are nearest-match rather than exact, and the return is 'path + html'. It omits the size/shape of the returned HTML, error behavior when no snapshot exists, and any read-only or permission context, leaving meaningful gaps.

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?

Two compact fragments, front-loaded with the operation and followed by cadence and return shape; nothing is wasted. The telegram style makes it slightly harder to parse than a full sentence, but it is appropriately sized for a one-parameter tool.

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

Completeness3/5

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

For a single-parameter read tool with no output schema, cadence and return shape are the critical missing pieces, and both are covered. Gaps remain around empty-result behavior and whether the HTML blob is large, which an agent would want to know before calling.

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?

The single t_ms parameter has 0% schema description coverage, so the description must supply meaning, and 'timeline ms' does clarify both the unit (milliseconds) and the timeline frame of reference. It could go further by stating what happens for timestamps between snapshots, but the essential semantic is present.

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: it fetches a DOM snapshot's HTML closest to a given timeline position. That is distinguishable from siblings like get_body and get_shot, though the description never explicitly contrasts them, so it stops short of a 5.

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 parenthetical '(snapshots at nav/mark/every 30s)' implies when this tool is useful and its resolution limit, so an agent can infer that arbitrary timestamps return the closest capture. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative for full-page body content or screenshots.

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