Skip to main content
Glama

Compare With Published Source

compare_published_source
Read-only

Read-only: the source changes a publish now would ship. Current saved code vs the live release (or release): both source digests (equal = identical) and every changed file with both sha256s, paged by offset; diffs only for the paths given. Paid plans.

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": {
      "projectId": "<projectId>"
    },
    "name": "compare_published_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffsNoPaths to diff.
offsetNo
releaseNoRelease id. Default: live.
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior. Beyond that, the description discloses important behavior: both source digests, changed files with both sha256s, offset paging, path-limited diffs, and the paid-plan requirement.

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?

The description is front-loaded with the read-only scope, then compactly covers comparison targets, outputs, paging, diff filtering, and plan requirements. It is dense but every clause carries relevant information.

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?

Without an output schema, the description does a good job explaining the return content: digests, changed files, sha256 pairs, and paging. The main remaining gap is that projectId, a required parameter, is not described.

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 50%, and the description adds useful semantics for offset paging and diffs limited to given paths. However, the required projectId parameter remains unexplained, and the release default is already covered by the schema.

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?

The description states a specific comparison operation: current saved code versus the live release (or a specified release), focused on changes a publish would ship. This clearly distinguishes it from publishing or status-checking siblings by describing exactly what is compared and returned.

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?

It gives a clear usage context: read-only comparison of saved source against the live/published release, with diffs limited to specified paths and a paid-plan requirement. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear.

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