Skip to main content
Glama
Sign In
Hive Web

Hive Web

by YegorMy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

action_web_close

Terminate an active Playwright browser session to free resources and end automation tasks.

Instructions

Close a live Playwright browser session.

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>"
    },
    "name": "action_web_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 only states 'close', which indicates termination but does not disclose side effects, prerequisites (e.g., session must exist), error conditions, or resource cleanup. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words. It is appropriately sized for a simple action, though it could add more value without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, low parameter coverage, and an output schema that is not referenced, the description is incomplete. It does not explain prerequisites, behavior upon invocation, or the context in which the tool is used, leaving gaps for an AI agent.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention the session_id parameter at all. It fails to explain its purpose, format, or how to obtain it, leaving the agent without necessary guidance.

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 'Close a live Playwright browser session' uses a specific verb ('close') and identifies the resource ('live Playwright browser session'). It clearly distinguishes from sibling tools like action_web_session_create (create) and action_web_navigate (navigate).

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?

The description implies the tool is used to end a browser session, providing clear context. However, it lacks explicit exclusions or alternatives (e.g., when not to use it or what to use instead for other session-related operations).

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