Skip to main content
Glama
ClintMoody

deep-think-mcp

by ClintMoody

move_session

Move a session file to a new absolute path; fails cleanly if destination exists (unless force=true), is unwritable, or missing.

Instructions

Move a session's file to new_path.

    `new_path` must be an absolute path (`~` is expanded). If it names
    an existing directory, the session moves into that directory under
    its current filename. Fails cleanly -- without touching the
    session or the filesystem -- if the destination already exists
    (unless `force=true`), isn't writable, or doesn't exist. `force`
    accepts a real bool or a word ("true"/"yes"/...) -- tolerant input.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNo
new_pathYes
session_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It thoroughly explains failure conditions (destination exists without force, not writable, etc.), tolerant input for 'force', and path expansion. Only minor gap is lack of mention about return value or side effects beyond file move.

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?

Description is front-loaded with the core action, uses clear sentence structure, and every sentence adds value. No wasted words.

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?

Given only 3 simple parameters, the description covers most aspects: path handling, force behavior, failure modes. Output schema exists so return values need not be described. Slightly incomplete on session_id specification, but overall sufficient.

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?

Schema has 0% description coverage (no property descriptions), so description must compensate. It effectively documents 'new_path' (absolute path, directory behavior) and 'force' (tolerant input). 'session_id' is not detailed, but its purpose is clear from context. Overall adds significant meaning beyond schema.

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?

Description clearly states the verb 'move' and the resource 'session file', specifies the key parameter 'new_path', and distinguishes the action from other operations like start or resume. The purpose is 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?

Description implies when to use this tool (to move a session's file), but does not explicitly contrast with sibling tools or provide when-not-to-use guidance. Given that siblings are diverse session management tools, the omission of explicit differentiation is a gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ClintMoody/deep-think-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server