Skip to main content
Glama
Sign In
smart-fork

smart-fork

by recursive-vibe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get-session-clusters

Retrieve all session clusters and their metadata to navigate past conversations and identify fork points for resuming context.

Instructions

Get all session clusters and their metadata

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-session-clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Get all' implies a read operation, but no further traits are disclosed (e.g., authorization, rate limits, or side effects). The minimal description does not add value beyond the tool name.

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?

The description is a single, clear sentence with no wasted words. It effectively communicates the tool's purpose in a front-loaded manner.

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?

For a simple parameterless retrieval, the description is arguably adequate but lacks detail on what 'metadata' encompasses. Given the presence of sibling tools like 'cluster-sessions' and 'get-cluster-sessions', more context would help an agent choose correctly. The lack of an output schema further reduces completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters in the input schema (0 params, 100% coverage). The description correctly adds nothing about parameters since none exist. Baseline 4 is appropriate as there is no additional semantic burden.

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 the resource 'all session clusters and their metadata'. It distinguishes from siblings like 'get-cluster-sessions' (which likely returns individual sessions in a cluster) by focusing on clusters themselves. However, it does not explicitly differentiate from other cluster-related tools like 'cluster-sessions'.

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 is provided on when to use this tool versus alternatives. The description does not mention any context, exclusions, or prerequisites. For example, it does not clarify whether to use this before 'cluster-sessions' or 'get-cluster-sessions'.

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