Skip to main content
Glama
Sign In
verifiable-thinking-mcp

verifiable-thinking-mcp

by CoderDayton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_session

Retrieve structured reasoning sessions in full, summary, or compressed formats to analyze cognitive processes and detect thinking patterns.

Instructions

Get session: full/summary/compressed format

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": {
      "format": "<format>"
    },
    "name": "get_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNoSession ID (uses active if omitted)
formatYesFormat: full (all), summary (overview), compressed (key only)summary
branch_idNoFilter by branch ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral context. It mentions format options but doesn't disclose what data each format returns, whether this requires authentication, if there are rate limits, or how the 'active' session fallback works. The description is insufficient for a tool with no annotation coverage.

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?

Extremely concise single phrase with zero wasted words. The description is front-loaded with the core purpose and includes essential format information in a compact format.

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

Completeness2/5

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

For a tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'session' represents in this context, what data is returned in each format, or how the tool behaves when session_id is omitted. The description should provide more context given the lack of structured metadata.

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 the schema already documents all three parameters thoroughly. The description adds minimal value by mentioning format options, but doesn't provide additional semantic context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the verb 'Get' and resource 'session', with the additional detail about format options (full/summary/compressed). It distinguishes from siblings like 'clear_session' (destructive) and 'list_sessions' (multiple sessions), but doesn't explicitly contrast with 'compress' or 'scratchpad'.

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?

No guidance on when to use this tool versus alternatives like 'list_sessions' or 'scratchpad'. The description mentions format options but doesn't explain when each format is appropriate or any prerequisites for use.

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

Deploy Server

Other Tools