Skip to main content
Glama
Sign In
smart-fork

smart-fork

by recursive-vibe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get-session-summary

Retrieve a concise summary of a past session to quickly understand its content without reading the entire transcript. Ideal for resuming context in semantic search or session forking.

Instructions

Get a quick summary of a session's content without reading the full session

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-summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session ID to get summary for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states 'quick summary' but does not specify return format, whether it's a read-only operation, or any performance implications. Minimal behavioral context beyond the core function.

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?

Single sentence, 14 words, front-loaded with the core action. Every word adds value. No redundant or missing elements. Highly efficient.

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 simple tool with one parameter and no output schema, the description adequately covers the purpose and basic behavior. It could mention the output format or limitations for completeness, but given the low complexity, it is sufficient.

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 only parameter, session_id, is fully described in the schema (100% coverage). The description adds context that the summary is 'quick' and avoids reading the full session, which provides some added meaning beyond the schema, but not significantly more.

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 identifies the verb 'Get', the resource 'summary of a session's content', and distinguishes from siblings like 'get-session-preview' by emphasizing 'quick' and 'without reading the full session'. It is specific and unambiguous.

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?

The description implies using this tool for a quick overview, but does not provide explicit guidance on when to choose it over alternatives like 'get-session-preview' or 'get-similar-sessions'. No exclusions or when-not-to-use are given.

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