Skip to main content
Glama

get_session_log

Read-only

Retrieves the 5250 session transcript log—connects, key presses, reconnects, and optional screens—so you can retrace what happened, even after a disconnect.

Instructions

The session's transcript: connects, fills (passwords masked), keys, flows, reconnects and recordings, newest last. Useful to retrace what happened, also after a disconnect.

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

Input Schema

NameRequiredDescriptionDefault
lastNohow many entries
screensNoalso include the screens the host sent (long)
sessionNosession name; lets you run several side by sidemain

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds genuinely non-obvious behavior: secrets are masked in fill entries, entries are ordered newest last, and the log remains readable after a disconnect. These are useful disclosures beyond the annotations, though nothing is said about retention limits, log size, or whether the transcript is bounded.

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?

Two short sentences with no filler; the content list and the newest-last ordering arrive before the usage hint. The comma-heavy enumeration is dense but each item earns its place by telling the agent what kinds of events to expect.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return shape needn't be described, and annotations cover the safety profile. The description still contributes the things structured fields cannot express — masking of passwords, ordering, and post-disconnect availability — so an agent has enough to call this correctly and interpret the result.

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 `last`, `screens`, and `session` are already fully documented in the schema, including defaults and bounds. The description adds no parameter-level meaning beyond that — the mention of fills/reconnects implies scope but does not clarify what `last` or `screens` actually change. Baseline 3 applies.

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?

The description identifies the resource precisely — the session transcript — and enumerates the event classes it contains (connects, fills, keys, flows, reconnects, recordings), which lets an agent distinguish it from siblings like get_screen or viewer. It never states the operation as a verb (fetch/return), so it is slightly indirect, but the noun phrase plus contents list is unambiguous about what you get back.

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?

'Useful to retrace what happened, also after a disconnect' gives a real usage scenario and a valuable edge case (log survives disconnects). However, it names no alternative and no exclusion — it does not say when to prefer get_screen or wait over reading the log, or that `screens` is the way to get screen payloads. Guidance is implied rather than directional.

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