Skip to main content
Glama

Compare deployment revisions

get_deployment_changes
Read-onlyIdempotent

Compares a local base revision with the current project revision. Returns remote file-change counts, sample paths and publication time; local unuploaded edits are outside this comparison.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
base_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description's added value is the comparison semantics: it compares remote state only and explicitly excludes local unuploaded edits, which is a real behavioral caveat an agent would otherwise get wrong. It does not mention permissions, rate limits, or how large the change set may be, keeping it short of a 5.

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?

Two sentences, no filler, with the core comparison stated first and the exclusion trailing as a qualifier. Every clause carries information the caller needs.

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-only, non-destructive tool with no output schema, the description covers what is compared and roughly what comes back. The remaining hole is the base_revision value domain, which is neither in the schema nor the description.

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 50%: project_id has a rich pattern-plus-guidance description, while base_revision has no schema description at all and permits integer, digit-string, or null. The description labels it a 'local base revision' but never explains what the value is drawn from or what null means, so it only partly compensates for the coverage gap.

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 gives a specific verb and resource: 'Compares a local base revision with the current project revision', and names the returned artifacts (file-change counts, sample paths, publication time). It is clearly distinguishable from mutation siblings like begin_deployment or finalize_deployment, but it never names get_deployment_status, which is the closest read-only alternative.

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 can infer this is a pre-deployment inspection step, and the note that 'local unuploaded edits are outside this comparison' sets a scope boundary. There is no explicit when-to-use statement and no guidance on choosing between this and get_deployment_status or list_releases.

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