Skip to main content
Glama
Sign In
sessions-mcp

sessions-mcp

by danielamiao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unshare_session

Revoke a session's shared link to stop access instantly. Disable the public share link for an AI coding session.

Instructions

Revoke a session's share link — the link stops working immediately.

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

Input Schema

NameRequiredDescriptionDefault
session_idYesthe session_id to unshare

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: the link stops working immediately. However, it omits other potentially relevant details such as irreversibility, permission requirements, or whether the session itself is affected. This is acceptable for a simple tool but lacks depth.

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 a single, concise sentence that is front-loaded with the action and effect. Every word earns its place, with no redundancy.

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?

The tool has only one parameter, no output schema, and no annotations, so the description needs to convey the core behavior, which it does. It would benefit from a note about whether the action is reversible or affects the session itself, but for a simple revocation it is largely complete.

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 100%, so the baseline is 3. The description does not add meaningful parameter details beyond what the schema already states ('the session_id to unshare'), and the only clue is that the session_id corresponds to a session with a share link.

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 uses a specific verb 'Revoke' and identifies the resource as 'a session's share link', clearly distinguishing it from sibling tools like share_session. It also states the immediate effect, making the purpose explicit and unambiguous.

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 clearly implies when to use the tool (to stop sharing a session) and contrasts with share_session through the verb 'revoke'. However, it does not explicitly name alternatives or exclusions, so it falls short of a 5.

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