Skip to main content
Glama
Sign In
Mcp-DOM

Mcp-DOM

by IrMaho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_session

Remove a stored recording session by its unique identifier to clear DOM mutation history and free up storage.

Instructions

Delete a recording session from storage.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "delete_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesUnique identifier of the recording session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Delete' without mentioning whether deletion is permanent, whether it affects associated data, or what happens if the sessionId does not exist.

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 concise sentence with no wasted words. It is front-loaded with the verb and resource, though it is so brief that it misses important behavioral context.

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?

The tool is simple with one well-documented parameter, so the description is minimally adequate for invocation. However, as a destructive operation with no annotations or output schema, it would be more complete if it noted irreversibility and side-effects.

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

Parameters3/5

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

The schema already provides 100% coverage of the only parameter, sessionId, with a clear description. The tool description adds no additional parameter semantics, but none are needed beyond 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 states a specific verb ('Delete') and a clear resource ('a recording session from storage'), making the tool's purpose immediately obvious. It also distinguishes itself from sibling read/export/import tools by explicitly naming deletion as the action.

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?

The description gives no guidance on when to use this tool versus alternatives such as export_session or get_session. It also does not mention prerequisites, consequences, or scenarios where deletion should be avoided.

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