Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

关闭上下文

context_close
Destructive

Close and destroy a browser context, clearing its tabs and cookies.

Instructions

关闭并销毁一个多账号上下文（其标签页与 cookies 一并清除）。

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": {
      "context_id": "<context_id>"
    },
    "name": "context_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
context_idYes

Output Schema

NameRequiredDescriptionDefault
okYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the destructive nature is known. The description adds value by specifying that tabs and cookies are cleared, giving more concrete behavioral detail. However, it does not mention irreversibility or potential side effects on other contexts, so it is adequate but not exhaustive.

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, clear sentence that conveys the core action and its effects without unnecessary words. It is appropriately concise and front-loaded with the main verb.

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

Completeness3/5

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

For a simple destructive action with a single parameter, the description covers the essential behavior. However, it could mention that the context must exist and that the operation is irreversible, but given the output schema exists and annotations cover destructiveness, this is a minor gap.

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

Parameters2/5

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

The schema has zero description coverage, and the description does not mention the context_id parameter. The parameter is a simple string, and its purpose is inferable from the tool name, but the description fails to explicitly connect it to the parameter, so the agent gets no extra semantic help.

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 action: closing and destroying a multi-account context, explicitly mentioning that tabs and cookies are cleared. It is specific about the resource and the effect, and it is distinct from sibling tools like context_new or cookies_clear.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention that browser_close is for browser sessions, nor does it warn about prerequisites like an existing context. The description only states the action, not the conditions for use.

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