Skip to main content
Glama

project_diff_versions

Read-onlyIdempotent

Compare two preserved deploy versions of a project. Returns per-file added / removed / changed paths, plus truncated text previews for changed files. After a 409 VERSION_CONFLICT it shows what the other deployer shipped, ahead of merging and retrying.

Both versions must still exist in the preserved-snapshot window (the platform keeps the most recent 10 versions). project_deploys shows whether both numbers are available.

Example:

{ "project_id": "my-saas", "from": 46, "to": 47 }
// Returns: {
//   from: 46, to: 47,
//   added:   [{ path: "api/billing.ts", size: 1244 }],
//   removed: [],
//   changed: [{ path: "index.html", from_size: 980, to_size: 1102, from_preview: "<html>...", to_preview: "<html>..." }],
//   functions: { added: ["api/billing.ts"], removed: [], changed: [] },
//   functions_changed: true
// }

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": {
      "project_id": "<project_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "project_diff_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe later version number (e.g. current_version from the 409 response, or project_get().version)
fromYesThe earlier version number (e.g. your last expected_version)
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds behavior not in the annotations: previews are truncated, only versions inside a preserved-snapshot window of the most recent 10 can be compared, and the tool exists to reconcile a 409 conflict. Those are exactly the constraints an agent needs before calling and would otherwise discover only via an error.

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?

Front-loads the purpose and return shape in the first two sentences, then the conflict scenario, then constraints. The example block is long relative to the prose and partly duplicates the schema parameter docs, but it does carry the return shape that no output schema provides, so it earns most of its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates fully with a worked example showing added/removed/changed arrays, size and preview fields, and the extra functions_changed summary. Combined with the retention-window caveat and the conflict-recovery context, an agent has everything needed to call this correctly on the first attempt.

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%, and the schema already explains that 'from' is the earlier expected_version and 'to' the later current_version from the 409, as well as the flexible project_id resolution. The description's example restates the same three-field call without adding syntax or edge-case meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Compare two preserved deploy versions of a project') and immediately enumerates what it produces: per-file added/removed/changed paths plus truncated previews. An agent can distinguish this from project_rollback or project_restore_version purely from the text, since it is a read-only comparison rather than a state change.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a concrete trigger scenario ('After a 409 VERSION_CONFLICT it shows what the other deployer shipped, ahead of merging and retrying') and names project_deploys as the pre-check for version availability. What is missing is an explicit exclusion — it never says when not to reach for this tool (e.g. for a single-version inspection or a plain file listing).

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