Skip to main content
Glama

Coline

Get a Code session

get_code_session
Read-onlyIdempotent

Reads one Code session: its task, plan, checks, preview and change request.

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": {
      "workspace": "<workspace>",
      "sessionId": "<sessionId>"
    },
    "name": "get_code_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesCode session id from list_code_sessions.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
planYes
taskYes
stateYes
checksYes
projectYes
sessionIdYes
previewUrlYes
statusLineYes
changeRequestUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds a content inventory of the response, which is useful framing but overlaps the existing output schema rather than disclosing behavior like scoping, permissions, or error cases.

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 the verb, scope, and returned contents in order of importance. No filler, no restatement of the title.

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 two-parameter read tool with full schema coverage, rich annotations, and an output schema, the description supplies enough to call it correctly. The only shortfall is the absence of any note on invalid or unknown session ids, which matters little given the annotations.

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 description coverage is 100%, with both sessionId ("from list_code_sessions") and workspace ("slug from workspaces.list, e.g. acme") fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 ("Reads one Code session") and enumerates the payload (task, plan, checks, preview, change request), so the agent knows exactly what it retrieves. It stops short of distinguishing itself from the sibling list_code_sessions, leaving the singular-vs-list split implicit.

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: fetching the details of a session the caller already has an id for. There is no explicit when-to-use, no statement that this is not for listing sessions (that lives only in the sessionId schema text), and no prerequisites such as the session needing to exist or the workspace needing access.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources