Skip to main content
Glama

privacy_session_end

Close a privacy session's context, discard its cookies and storage, and verify cleanup without touching your ordinary browser profile.

Instructions

End a privacy session: close its context, discard its cookies/storage and VERIFY the cleanup. Your ordinary browser profile is never touched.

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

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and does a fair job: it discloses that the session context is closed, cookies and storage are discarded, cleanup is verified, and the ordinary profile is provably untouched. It omits what happens on an invalid or already-ended session_id and whether the call is idempotent.

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?

Two tight clauses, action and effects front-loaded, safety reassurance second. Every word earns its place and nothing is padded.

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?

For a one-parameter, annotation-free, no-output-schema teardown tool, the description says enough about the action and its destructive scope to call it correctly. The remaining gap — identifying what session_id is and how errors on stale sessions behave — is real but modest at this complexity.

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?

Schema description coverage is 0% for the single session_id property, and the description never mentions the parameter or its expected form. It only implies the identifier refers to a privacy session, which is marginal added meaning over the schema's bare string type and title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('End a privacy session') and then enumerates the concrete effects: close context, discard cookies/storage, verify cleanup. That clearly separates it from lifecycle siblings like privacy_session_open, privacy_session_start, and privacy_session_snapshot, though it does not name them explicitly.

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?

Usage is only implied — 'End a privacy session' tells an agent this is the teardown step, and 'Your ordinary browser profile is never touched' hints at when it is safe to use. There is no explicit when-to-use/when-not guidance and no named alternative for the open/start siblings, leaving the agent to infer the lifecycle ordering.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.