Skip to main content
Glama

session_close

Release leases and revoke the current session, optionally for all actors or a specified actor handle.

Instructions

Release leases and revoke the current session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "session_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
all_actorsNo
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the two concrete effects — leases are released and the session is revoked — but it says nothing about irreversibility, whether the session can be resumed, what happens to still-running child actors, or whether any authorization is needed.

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?

A single short sentence with no filler and the effect front-loaded. It is efficient, but its brevity comes at the cost of the missing scope information rather than being perfectly tight.

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?

An output schema exists, so return values need not be described, but for a session-terminating operation with no annotations and two undocumented scope parameters, the definition omits too much. An agent cannot tell how broad the revocation will be or whether the action is reversible.

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?

Schema description coverage is 0% for two parameters, and the description never mentions them. The scope distinction between closing a single actor via actor_handle and closing everything via all_actors is left entirely undocumented, forcing the agent to guess the semantics of a destructive scoping flag.

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 two concrete actions with specific verbs and resources: releasing leases and revoking the current session. The resource ('current session') is unambiguous, though it does not explicitly distinguish itself from other lifecycle siblings like delegate_child or register_agent.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites, and no reference to alternative tools. Usage is only implied by the word 'close' — an agent must infer that this is the terminal cleanup step for a session.

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