Skip to main content
Glama

get_session

Read-onlyIdempotent

Open one of the coach's own saved training sessions by id (from list_my_sessions): title, date, topic, age group, duration, the plan text and a short summary of each saved practice. Use it to edit the wording with the coach.

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

Input Schema

NameRequiredDescriptionDefault
session_idYesSaved session id (UUID) returned by list_my_sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value the annotations cannot: the exact return payload, which matters because there is no output schema. It does not discuss permission behavior if an id belongs to another coach, though 'the coach's own' implies ownership scoping.

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 front-loaded sentence that leads with the action and id source before listing return fields; no filler. The return-field list is slightly long but each item tells the agent what to expect, so nothing is wasteful.

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 tool with no output schema, the description correctly compensates by describing the returned session shape and its edit-oriented purpose. Only a note on behavior for invalid or inaccessible ids is missing, which 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?

Schema coverage is 100% and the session_id property already documents the UUID provenance. The description merely repeats that the id comes from list_my_sessions, adding no format or validation detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Open one of the coach's own saved training sessions by id', and enumerates exactly what comes back (title, date, topic, age group, duration, plan text, per-practice summaries). Naming list_my_sessions as the id source separates it cleanly from the sibling that enumerates sessions.

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?

Gives a concrete use case — 'Use it to edit the wording with the coach' — and points to list_my_sessions as the prerequisite for obtaining the id. It stops short of stating when not to use it (e.g. versus generate_session_plan for new sessions), so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources