Skip to main content
Glama
Sign In
FishClaw MCP

FishClaw MCP

by TnoobT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

restart_browser

Restart the Playwright browser process to recover from closed or unresponsive browser sessions without restarting the MCP server. After restart, re-authenticate login status before continuing operations.

Instructions

重新初始化 Playwright 浏览器进程，无需重启 MCP 服务器。 当出现以下情况时调用：

  • 浏览器窗口已被手动关闭

  • 页面长时间无响应或报错

  • 提示"浏览器进程已关闭"等异常 重启后需重新调用 login 验证登录状态，再继续执行后续操作。

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": "restart_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the browser restarts and session state is lost by requiring login re-validation. It could mention that open tabs or in-progress actions are lost, but the need to re-login implies this.

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 brief, uses bullet points for clarity, and front-loads the main purpose. Every sentence contributes actionable information with no unnecessary 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?

Given zero parameters and no annotations, the description fully covers the tool's purpose, usage conditions, and post-invocation steps. It is complete for the tool's complexity and context.

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 input schema has zero parameters, and schema coverage is 100%. The description adds no parameter meaning because there is nothing to add. Following the rubric, 0 parameters yields a baseline of 4.

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 explicitly states the tool reinitializes the Playwright browser process without restarting the MCP server, and distinguishes it from sibling tools that manage items, login, etc. The verb 'reinitialize' and resource 'browser process' are specific and clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists three concrete scenarios (browser closed, page unresponsive, error message) and gives clear post-use instruction to re-call login. This provides explicit when-to-use guidance and a necessary follow-up action.

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