Skip to main content
Glama

Baseline Verify

baseline_verify
Read-only

Verify whether a rebuild reproduces a pinned baseline by re-resolving pinned items and comparing revisions and content fingerprints; catches drifted or missing inputs.

Instructions

Verify a rebuild against a pinned baseline (issue #142, C3) — the reproducible- rebuild gate. Re-resolves every pinned item from the current registry + artifacts and checks it still matches the pinned rev AND content fingerprint; a drifted input (changed bytes, a bumped rev, a vanished item) is caught, never silently accepted.

baseline: path to the baseline sidecar. registry: path to the current items.json sidecar. base_dir: artifact root for fingerprinting (defaults to the registry's directory).

Returns {ok, label, drifted (item/field/expected/actual), missing} — ok is True iff the rebuild reproduces the baseline exactly.

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": {
      "baseline": "<baseline>",
      "registry": "<registry>"
    },
    "name": "baseline_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_dirNo
baselineYes
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

A4.5/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld=false; the description adds substantial behaviour: it re-resolves every pinned item from the current registry and artifacts, checks both rev and content fingerprint, and treats changed bytes, bumped revs, or vanished items as drift rather than silently accepting them. That is real disclosure beyond the annotation.

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?

Front-loaded with the core purpose, then parameters, then return shape — a clean structure with no filler. The issue-tracker reference '(issue #142, C3)' is noise for an invoking agent but costs only a few tokens.

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?

There is no output schema, but the description spells out the return shape {ok, label, drifted, missing} and the ok semantics, and it explains the verification inputs. Only minor gaps remain, such as whether artifacts must exist locally and what happens when base_dir is omitted in practice.

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 25% (only workspace is documented in-schema), so the description must compensate. It does for baseline, registry, and base_dir (including its default of the registry's directory), but leaves the workspace parameter entirely unexplained.

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?

States a specific verb and object ('verify a rebuild against a pinned baseline') and frames the tool's role as 'the reproducible-rebuild gate', which distinguishes it from sibling baseline_create and from items_validate/items_resolve. An agent can tell what this does without opening the schema.

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?

The 'gate' framing plus the description of what constitutes a drifted input makes the usage context clear (run after a rebuild, before release). It never explicitly names alternatives such as baseline_create or release_package, nor states exclusions, so it falls short of a 5.

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