Skip to main content
Glama

Snapshot a branch

argon_snapshot_create
Idempotent

Create a snapshot of a branch's current head so later reads replay only the delta above it, keeping reviews focused on changes.

Instructions

Snapshot a branch at its current head so reads replay only the delta above it.

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

Input Schema

NameRequiredDescriptionDefault
branchYesBranch name
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=false, destructiveHint=false, and idempotentHint=true, so the safety and repeat-call profile is covered. The description usefully explains the functional effect on later reads, but says nothing about whether an existing snapshot at the same head is reused or replaced, or about any cost or limits.

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?

A single front-loaded sentence stating the action and its downstream consequence, with essentially no filler. It is short enough that the absence of structure is not a 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?

For a two-parameter tool with full schema coverage and no output schema, the description covers the core action and its read-path effect. It still leaves gaps on snapshot lifecycle semantics (reuse versus replacement, visibility to other agents), which matter for a state-mutating-but-non-destructive operation.

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% with both required parameters ('project', 'branch') documented in the schema. The description only implicitly references the branch concept and adds no format, naming, or scoping detail beyond what the schema already provides; 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 ('Snapshot a branch') plus the scope ('at its current head') and the effect ('reads replay only the delta above it'). An agent can tell it creates a snapshot distinct from sibling creation tools like argon_pin_create or argon_sandbox_create, though no sibling is named to sharpen the contrast.

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?

The implied usage condition is present: call this when you want subsequent reads to replay only the delta above the branch head. There is no explicit when-not guidance, no prerequisite discussion, and no named alternative among the many sibling creation tools, so routing must be inferred.

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