Skip to main content
Glama
Sign In
wraith-mcp

wraith-mcp

by Koreahwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

snapshot

Retrieve the current page's interactive elements as an indexed list for clicking or typing. Re-run after page changes to keep the list accurate.

Instructions

Return the current page's interactive elements as [index] <tag> text.

Pass an index to click/type_text. Re-run after the page changes.

Args: session_id: Session to inspect (default: "default")

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
session_idNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full safety/disclosure burden. It adds useful behavioral context: the snapshot is an indexed list of interactive elements, indices are tied to the current page state, and stale results require a re-run. It doesn't explicitly state that this is a read-only operation, but the phrase 'Return' and the provided workflow imply no side effects.

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 segments with no filler: the main purpose, a usage tip, and a parameter note. The most important information appears first and the entire description is under 70 words.

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?

For a single-parameter, read-only tool with an output schema, the description covers the core contract: what is returned, how to interpret it, when to refresh, and how to address a session. Nothing essential is missing.

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 schema only defines `session_id` with a default and no descriptive help text (0% coverage). The description's Args section adds meaning by identifying it as 'Session to inspect', which clarifies the parameter's role beyond the schema's bare type and default.

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 opens with a specific verb+resource ('Return... interactive elements') and defines the output format `[index] <tag> text`, which distinguishes it from sibling read tools like get_content or screenshot.

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 explicitly instructs to pass an index to click/type_text and to re-run after the page changes, giving clear context for when to use it and how the result should be consumed. It doesn't name exclusions or alternative tools, but the usage note makes the intended scenario clear.

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