Skip to main content
Glama

Coline

Read a Code session's changes

get_code_diff
Read-onlyIdempotent

Reads the changes a Code session made so far, as a unified diff with the files it touched.

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_diff"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
diffYes
summaryYes
truncatedYes
changedFilesYes

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add that results are 'so far' (an in-progress snapshot, not a final patch) and that output is a unified diff with touched files, but says nothing about pagination, truncation, or behavior on a session with no changes.

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 sentence that front-loads the action, then the scope ('so far'), then the output format. Nothing is redundant or padded.

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 two-parameter read with full schema coverage, an output schema, and read-only annotations, the definition covers what the tool returns and that it is a live snapshot. Minor gaps remain around diff scope (cumulative vs. last turn) and empty-session behavior, but nothing blocking for correct invocation.

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% and both parameters are documented in-schema, including where the sessionId and workspace slug come from (list_code_sessions, workspaces.list). The description adds no extra meaning about either parameter, so the baseline 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?

States a specific verb and resource ('Reads the changes a Code session made so far') plus the return shape (unified diff and files touched). It does not name or contrast with a sibling such as get_code_session or show_code, so an agent must infer the boundary, which keeps it below 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 Guidelines3/5

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

Usage is implied: use it when you want the diff produced by a Code session. There is no explicit when-to-use/when-not guidance and no mention of an alternative for viewing session state versus session changes, which is exactly the ambiguity a sibling like get_code_session would create.

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