Roundtable

Get Session

get-session

Read-onlyIdempotent

Get full details of a previous MCP session by ID. Returns the complete result including participant responses and moderator synthesis. Use list-sessions first to find session IDs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	Yes	The session ID to retrieve

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Session identifier
`prompt`	Yes	Original prompt text
`toolName`	Yes	Tool that was invoked
`createdAt`	Yes	Session creation timestamp
`durationMs`	Yes	Duration in milliseconds
`qualityScore`	Yes	AI-rated quality score
`totalCredits`	Yes	Total credits consumed

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedMar 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds value by specifying the return content (participant responses and moderator synthesis), though it doesn't mention error behavior or not-found cases.

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?

Three concise sentences front-load the purpose and return value, with a useful prerequisite note. No filler or redundancy.

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?

For a simple single-parameter read tool with strong annotations and an output schema, the description covers purpose, return contents, and how to find the ID. It is fully adequate.

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?

The input schema fully documents the single parameter 'session_id' with a description, so the description adds minimal extra semantic value. The phrase 'by ID' reaffirms the schema but does not enrich it.

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?

The description clearly specifies the action ('Get full details') and resource ('previous MCP session by ID'), distinguishing it from the sibling tool 'list-sessions' which lists sessions. It also states what the result contains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to use 'list-sessions first to find session IDs', providing clear sequencing and pointing to the alternative tool. This is direct when-to-use guidance.

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

All Roundtable tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

The tool set separates general consultation (consult-council) from specialized councils for tradeoffs, debugging, architecture, implementation planning, and code review. Session management and utility tools (logs, usage, models, sessions) are clearly distinct. Only minor potential overlap exists between consult-council and the specialized councils, but descriptions clarify the purpose of each.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., consult-council, get-session, list-models). Verbs are varied but predictable, and compound nouns are hyphenated consistently. No mixed conventions.

Tool Count5/5

13 tools is appropriate for a platform that offers multiple council workflows plus session, log, and usage management. Each tool addresses a distinct need without unnecessary bloat.

Completeness5/5

The server covers the full lifecycle of a council-based workflow: model discovery (list-models), execution (consult-council and specialized councils), session retrieval (list-sessions, get-session), sharing (get-thread-link, set-thread-visibility), and operational support (check-usage, get-logs). Missing delete/update session tools are minor and not essential for the core purpose.

Resources

Need Help?