Skip to main content
Glama
Sign In
wraith-mcp

wraith-mcp

by Koreahwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

screenshot

Capture a webpage and return a base64-encoded PNG. Provide a URL, and optionally enable full_page to include the entire scrollable content.

Instructions

Take a screenshot of a webpage and return it as base64-encoded PNG.

Keyless — navigates and captures directly, no LLM.

Args: url: URL to screenshot full_page: Capture the full scrollable page (default: visible viewport only)

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": {
      "url": "<url>"
    },
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
full_pageNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It discloses the output format (base64 PNG) and the keyless, direct capture behavior, but does not mention failure modes, page load handling, or limitations. This is minimal but not misleading.

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 three short sentences plus an Args list. Information is front-loaded, with the core purpose in the first sentence, and every phrase adds value. No filler or redundancy.

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 2-parameter screenshot tool with an output schema, the description covers core behavior, output format, and parameter semantics. It lacks some edge-case details (e.g., what happens on navigation failure), but is sufficient for the tool's simplicity.

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. The Args section explains both 'url' and 'full_page', with full_page's default clarified as 'visible viewport only'. It adds meaning beyond the raw schema, though the url explanation is slightly tautological.

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?

The description states 'Take a screenshot of a webpage and return it as base64-encoded PNG' – a specific verb and resource with output format. However, it does not explicitly distinguish from sibling tools like 'snapshot' or 'pdf', so it lacks explicit sibling differentiation.

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 mentions it is 'Keyless' and navigates/captures directly, but it does not provide explicit when-to-use vs alternatives like 'snapshot' or 'get_content'. Usage is only implied by the purpose.

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