Skip to main content
Glama

Get OpenCode session

opencode_session_get
Read-only

Retrieve metadata for one OpenCode session—title, agent, model, cost, tokens, timestamps, and outcome—to inspect or audit that session.

Instructions

Fetch one session's metadata: title, agent, model, cost, tokens, timestamps and outcome.

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>"
    },
    "name": "opencode_session_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes the safety profile, so the description only needs to add context beyond that. It usefully enumerates the returned metadata fields, but says nothing about what happens when the sessionID is unknown, whether the call is scoped to a workspace, or any cost/latency characteristics.

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?

A single front-loaded sentence with no filler; the verb and resource lead and the field list trails as supporting detail. Every clause earns its place.

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 single-parameter read tool with no output schema, listing the returned fields does the work an output schema would otherwise do, and the annotation covers safety. The remaining gap is the sessionID's expected form and error behavior for invalid IDs.

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?

There is one parameter with 0% schema description coverage, so the description must carry the meaning of sessionID — and it does not explain the ID's format, where to obtain it, or whether it is workspace-scoped. The phrase 'one session's metadata' only weakly signals that the parameter identifies a single session.

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?

States a specific verb ('Fetch') and resource ('one session's metadata'), then enumerates the fields returned (title, agent, model, cost, tokens, timestamps, outcome). 'One session' implicitly contrasts with the list sibling, but no alternative is named explicitly.

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?

Usage is only implied: an agent infers this is for retrieving a single known session rather than enumerating sessions. Nothing states when to prefer it over opencode_session_list or opencode_session_history, and no prerequisites or failure conditions are mentioned.

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