Skip to main content
Glama

Baseline Create

baseline_create
Destructive

Create an immutable labeled baseline snapshot of an items registry to pin artifact bytes for reproducible, byte-verifiable rebuilds.

Instructions

Pin a labeled, immutable BASELINE (issue #142, C3) — a {item: revision + content fingerprint} snapshot over an items.json registry (a git-tag / lockfile over the item graph) for reproducible rebuilds. The fingerprint pins the artifact BYTES, so a rebuild is verifiable byte-for-byte.

label: the baseline label (e.g. "v1.0"). registry: path to the items.json sidecar. items: optional subset of item ids to pin (default: every item). base_dir: artifact root for fingerprinting (defaults to the registry's directory). note: optional description. out: optional path — write the git-diffable baseline sidecar there.

Returns the baseline object. Deterministic: same state -> identical bytes.

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": {
      "label": "<label>",
      "registry": "<registry>"
    },
    "name": "baseline_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNo
noteNo
itemsNo
labelYes
base_dirNo
registryYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

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 and destructiveHint=true, so the description is not the sole carrier of the safety profile. It adds real context — immutability of the pinned snapshot, byte-level determinism ('same state -> identical bytes'), and that `out` writes a git-diffable sidecar — but it is silent on the key destructive behavior implied by destructiveHint: whether creating a baseline whose label already exists overwrites or fails.

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?

The core definition is front-loaded in the first sentence, then a clean one-line-per-parameter block, then return/determinism. Minor waste in the parenthetical '(issue #142, C3)' and the 'git-tag / lockfile over the item graph' aside, which an agent does not need in order to call the tool.

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 7-parameter mutation tool with no output schema and near-empty schema descriptions, the definition supplies purpose, per-parameter meaning, defaults, and a statement of what is returned plus its determinism guarantee. The gaps are overwrite/duplicate-label semantics and failure modes (missing registry, unknown item ids) — relevant given destructiveHint=true.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description carries the burden and mostly does: it defines label (with a "v1.0" example), registry, items (subset semantics plus default), base_dir (with its default), note, and out (what gets written where). Only the `workspace` parameter is left undocumented, and the `items` element type is clarified only loosely as 'item ids'.

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 concrete verb and resource — 'Pin a labeled, immutable BASELINE' — and explains the artifact as a {item: revision + content fingerprint} snapshot over an items.json registry, with an analogy (git-tag / lockfile). An agent knows exactly what is produced, but the description never names the counterpart baseline_verify or distinguishes this from items_* tools in the sibling list.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no mention of the alternative baseline_verify or of prerequisites (registry must exist, items must resolve). Usage must be inferred entirely from the semantic explanation of what a baseline is.

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

Deploy Server

Other Tools