Skip to main content
Glama
YogevKr

Wraith MCP Server

by YogevKr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

navigate

Open a URL and return an indexed snapshot of interactive elements. Automatically handles WAAP challenges and dismisses cookie banners.

Instructions

Open a URL and return an indexed snapshot of the page's interactive elements.

Automatically attempts WAAP challenges, including HUMAN/PerimeterX Press & Hold, and dismisses common cookie/consent banners. No separate challenge command is needed. If verification fails, navigation reports an error; do not assume clearance. Each line is [index]<tag role=...>text</tag>; use the index with click / type_text. Pass include_snapshot=false for a compact summary (saves tokens; call snapshot() when you need the list).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
include_snapshotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / include_snapshot
      Added value: +{
+  "default": true,
+  "title": "Include Snapshot",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses automatic WAAP handling, cookie/consent dismissal, failure behavior, and that successful verification should not be assumed if an error is reported.

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 front-loaded with the core action and then adds only operationally useful details. Every sentence earns its place, including the snapshot format and the compact-summary guidance.

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?

Despite having an output schema, the description still explains the relevant return format and how to consume indexes with other tools. It covers the key behaviors and parameter tradeoff an agent needs to invoke navigate correctly.

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 description must compensate. It clearly explains include_snapshot and its tradeoff, while url is self-evident from the name and purpose; more detail on accepted URL forms would be needed for a 5.

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 and resource: open a URL and return an indexed snapshot of interactive elements. It also differentiates itself from siblings by explaining that the returned indexes are used with click/type_text and that snapshot() is for listing when the compact summary is used.

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 gives clear usage context: no separate challenge command is needed, include_snapshot=false saves tokens, and snapshot() should be called when the full list is needed. It does not explicitly compare navigate against fetch or state when not to use it, so it falls just short of the highest bar.

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