Skip to main content
Glama
Sign In
wraith-mcp

wraith-mcp

by Koreahwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tabs

List current browser pages, open a URL, or close a page by ID in a persistent session. Use session ID and action to manage browser state.

Instructions

Manage browser tabs within a persistent session.

Args: session_id: An existing session ID action: One of "list", "open", "close" url: URL to open (action="open"; validated http/https) target_id: Tab target_id to close (action="close"; from action="list")

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": {
      "session_id": "<session_id>",
      "action": "<action>"
    },
    "name": "tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
actionYes
target_idNo
session_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It explains each action and parameter, including URL validation, but does not disclose side effects, session requirements beyond 'existing', or error behavior. It adds useful context but lacks depth.

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 structured with an Args block, with no fluff. Every sentence earns its place, making it easy to parse.

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?

The description covers all required aspects for usage, and the output schema covers return values. It lacks some detail on error handling or session state, but is otherwise complete for a simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description compensates by explaining all parameters: session_id, action, url (with validation), and target_id (sourced from list). This fully maps the schema.

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 clearly states the tool manages browser tabs within a persistent session and enumerates the supported actions (list, open, close). This is specific and distinguishes it from sibling tools like navigate or browse.

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 implies usage for tab management within a session but does not explicitly state when to choose this over alternatives or provide exclusions. The context of a persistent session and action list gives some guidance, but no explicit comparisons are made.

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