Skip to main content
Glama

Get a session

get_session
Read-only

The current state (state.text in plain language, state.data as JSON), whose turn it is, the chat and, once over, the result.

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
sinceNoOnly chat messages with an id above this: pass the last message id you have seen
session_idYesThe session_id returned by start_game

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world safety, so the bar is lower. The description earns credit by disclosing the return payload — plain-language state.text, structured state.data, whose turn it is, chat, and a final result — which annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the most important content (state), but as an unpunctuated fragment it reads as a payload listing rather than an action statement, which slows an agent trying to confirm purpose.

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

Completeness3/5

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

With no output schema, the description usefully sketches the return shape, but 'the result' is undefined and the incremental-polling contract is left entirely to the schema. Adequate but with clear gaps for a tool whose main job is returning structured data.

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%, so both parameters are fully documented in the schema, establishing a baseline of 3. The description mentions 'the chat' but does not explain the incremental `since` cursor behavior that the schema documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase listing return contents rather than a statement of what the tool does; only the title ('Get a session') supplies the verb. An agent can infer it reads session state, but nothing distinguishes it from siblings such as get_game or wait_for_turn.

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 guidance on when to call this versus get_game, wait_for_turn, or suggest, all of which plausibly overlap. No prerequisites or polling cadence are mentioned.

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