Skip to main content
Glama

Get Session

get_session
Read-onlyIdempotent

Retrieve a recording session by ID to check its live status and confirm whether the output file exists on disk.

Instructions

Inspect a single recording session by id, including live status and whether its output file exists on disk.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession id returned by start_recording.

Output Schema

NameRequiredDescriptionDefault
idYes
aliveYes
statusYes
fileExistsYes
outputPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.47.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "alive": {
      +      "type": "boolean"
      +    },
      +    "fileExists": {
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "outputPath": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "status",
      +    "outputPath",
      +    "alive",
      +    "fileExists"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context by saying it reports live status and checks whether the output file exists on disk, which is beyond what the annotations provide.

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?

One front-loaded sentence with no filler. It conveys purpose and the two most important pieces of returned information without 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?

For a one-parameter read-only lookup with annotations and an output schema, the description covers enough to call correctly and understand what it returns. It could be slightly stronger by noting behavior when the session is missing, but that is a minor 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?

There is one parameter with 100% schema description coverage, so the schema already explains that sessionId comes from start_recording. The description says 'by id' but adds no extra format, validation, or lookup semantics beyond the schema baseline.

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: inspect a single recording session by id, and adds that it reports live status and output-file existence. This clearly distinguishes it from list_sessions or the recording-control siblings, though it does not explicitly name alternatives.

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 implied: use it when you have a session id from start_recording and need to inspect that one session. There is no explicit when-to-use guidance, exclusions, or named alternative tool for related inspection needs.

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