Skip to main content
Glama

Diff a branch against its parent

argon_diff
Read-onlyIdempotent

Preview the documents and conflicts that would result from merging a branch into its parent, so you can review changes before deciding to merge or discard.

Instructions

Show what merging a branch into its parent would change: adopted documents and conflicts.

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": "<project>",
      "branch": "<branch>"
    },
    "name": "argon_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesBranch to compare against its parent
projectYesProject name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the bar is low. The description does add genuine value by naming the two output categories (adopted documents, conflicts), but says nothing about how conflicts are reported or how large a diff can get.

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?

One sentence, front-loaded with the purpose and ending with the colon list of what is returned; nothing is wasted. It is terse to the point of leaving the sibling-versus-sibling question unanswered, which is a content gap rather than a wording flaw.

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

Completeness3/5

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

With two fully documented parameters and a read-only annotation profile, most structured burden is already carried elsewhere. But there is no output schema, so the description is the only source on return values and it gives just two category names without form or structure.

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 defines both 'branch' ('Branch to compare against its parent') and 'project' ('Project name'). The description adds no meaning beyond that — 'project' is never mentioned — 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: show what merging a branch into its parent would change. The added clause 'adopted documents and conflicts' tells the agent what the diff reports, which is more than a restated title. It does not, however, distinguish the tool from argon_merge_preview, which by name could sound like the same read-only operation.

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 by the 'would change' framing — inspect before merging — with no explicit when-to-use, when-not, or named alternative. The most obvious ambiguity, this tool versus argon_merge_preview, is left for the agent to resolve.

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