Skip to main content
Glama

close_session

Close a live session to save any running recording, end the test attempt, dispose the engine, and stop app processes the session started.

Instructions

Close a live session: save a recording still running, end the attempt, dispose the engine, and stop the app processes the session started.

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

Input Schema

NameRequiredDescriptionDefault
sessionNoSession id from open_session; may be omitted only while one session is open

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.23.1

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare that this mutates state (readOnlyHint=false, openWorldHint=false); the description goes well beyond them by disclosing the concrete side effects: flushing an in-flight recording, ending the attempt, disposing the engine, and terminating spawned app processes. It stops short of stating irreversibility or failure behavior, which keeps it from a 5.

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?

A single front-loaded sentence with the core action first and the side effects in a compact list. Every clause carries distinct information; nothing is repeated or 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 teardown mutation with no output schema, the description covers the essential behavior and its consequences. It leaves unstated the error case (no open session) and whether the close is reversible or can be retried, a small but real gap.

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%, and the schema already explains that the session id comes from open_session and may be omitted while exactly one session is open. The description adds nothing about the parameter, so the baseline of 3 applies.

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?

"Close a live session" gives a specific verb and resource, and the four enumerated consequences (save recording, end attempt, dispose engine, stop app processes) make the tool's identity unmistakable. It reads as the direct counterpart to open_session, so an agent can distinguish it from the other siblings without inspecting any schema.

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?

The description implies the usage context (tearing down a session) but never says when to call it versus leaving a session open, nor what happens if no session is active. No alternatives or prerequisites are named, so the agent must infer the timing from the word "live".

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