Skip to main content
Glama
Sign In
wraith-mcp

wraith-mcp

by Koreahwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

click

Triggers the element at the specified snapshot index and returns a fresh snapshot, enabling step-by-step browser automation.

Instructions

Click the element with the given index (from snapshot). Returns a new snapshot.

Args: index: Element index from snapshot session_id: Session to act on (default: "default")

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": {
      "index": "<index>"
    },
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes
session_idNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description must carry the transparency burden. It discloses the main behavior and the fact that a new snapshot is returned, but it does not mention potential side effects (e.g., navigation, waiting for load) or error behavior for stale indices.

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 compact and front-loaded, with a one-sentence purpose followed by a clear Args block. Every line provides relevant information without redundant filler.

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?

For a simple click action, the description covers the core workflow: get snapshot index, click, receive a new snapshot. It could mention prerequisites like session creation, but the schema and default values fill some gaps, and an output schema exists.

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?

Schema coverage is 0%, so the parameter descriptions are essential. The description explains 'index' as an element index from a snapshot and 'session_id' as the session to act on with a default, adding meaningful context beyond the raw schema types.

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 states a specific verb ('Click'), a clear target ('the element with the given index (from snapshot)'), and the return value ('Returns a new snapshot'). This distinguishes it from sibling tools like type_text, scroll, and navigate.

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 phrase 'from snapshot' implies the prerequisite of obtaining a snapshot first, and returning a new snapshot suggests a refresh workflow. However, there is no explicit guidance on when to use this vs. alternatives or when not to use it.

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