Skip to main content
Glama

Move OpenCode session

opencode_session_move

Change the working directory of an existing session by providing its session ID and new absolute directory path.

Instructions

Change the working directory of an existing 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": {
      "sessionID": "<sessionID>",
      "directory": "<directory>"
    },
    "name": "opencode_session_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYesNew absolute working directory
sessionIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations supply only readOnlyHint=false, so the description carries most of the behavioral burden. It does not say whether conversation history or pending work survives the move, whether the session is interrupted, whether the path is validated, or what happens if the directory does not exist — all critical for a mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is the right shape for a simple two-parameter tool. Its brevity is appropriate in form even though the content is thin.

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 mutating session operation with no output schema, one minimal annotation, and half the parameters undocumented, the description should cover side effects, preconditions, and the outcome of the move. None of that is present, leaving the agent under-informed before invoking it.

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

Parameters2/5

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

Schema coverage is 50%: 'directory' is documented as a new absolute working directory, but 'sessionID' has no schema description and the description adds nothing about it. The description also adds no meaning beyond the schema — nothing about path format constraints, relative-path rejection, or how the ID is obtained.

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 names a specific verb and resource: 'Change the working directory of an existing session.' That is unambiguous and implicitly distinguishes it from siblings like create, delete, compact, and interrupt, which do not alter session cwd. It stops short of explicitly naming any alternative, which keeps it from a 5.

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?

There is no guidance on when to move a session versus creating a new one in the target directory, and no stated preconditions such as whether the session must be idle or whether the directory must already exist. The agent is left to infer all of this from a single sentence.

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