Skip to main content
Glama
Sign In
smart-fork

smart-fork

by recursive-vibe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get-similar-sessions

Find past sessions similar to a given session to detect duplicates or related work, enabling efficient context reuse.

Instructions

Find sessions similar to a given session (for detecting duplicates or related work)

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-similar-sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession ID to find similar sessions for
top_kNoMaximum number of similar sessions to return (default: 5)
include_scoresNoWhether to include similarity scores in output (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the purpose, omitting any details about how similarity is computed, side effects (presumably read-only), or constraints like performance. This is insufficient for an agent to understand the tool's behavior.

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, concise sentence that front-loads the action and purpose. Every word adds value, and there is no redundancy.

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?

Despite low complexity, the description fails to explain the return format, pagination (top_k), or what 'similar' means. Without an output schema, the description should cover these aspects to be complete. Sibling tool differentiation is absent.

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%, with each parameter having a description in the schema. The tool description does not add any parameter information beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states the tool finds sessions similar to a given session, with a specific use case for duplicates or related work. It uses a specific verb and resource, and it distinguishes from siblings like compare-sessions and 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 Guidelines3/5

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

The description implies usage for detecting duplicates or related work, but it does not explicitly say when to use this tool over alternatives. No exclusions or when-not-to-use guidance are provided.

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