Skip to main content
Glama

vicem_read_baton

Read-onlyIdempotent

Reads the current .vicem/BATON.md handoff document and warns when git HEAD has drifted from the recorded baton commit, so you can inspect goals, next steps, and the Diet Ledger before editing.

Instructions

Reads the current .vicem/BATON.md handoff document and checks whether git HEAD has drifted from .vicem/baton.json. Use first when starting a handed-off session to inspect the goal, next steps, and Section 6 Diet Ledger index; do not use to create a baton (vicem_create_baton), restore an individual function body (vicem_rehydrate), or validate code diffs (vicem_check_guard). Read-only local operation (no auth, rate limits, or file mutations). Returns the full BATON.md text with isError=false; if git HEAD moved ahead of the baton commit, the call still succeeds and prepends a "> ⚠️ [STALENESS DRIFT WARNING]" banner with both commit hashes so you can check git diff before editing. Returns isError=true if .vicem/BATON.md does not exist.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vicem_read_baton"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only and non-destructive annotations, it discloses that the operation is local with no auth, rate limits, or file mutations. It also explains the return behavior: full BATON.md text with isError=false, a staleness drift warning banner with both commit hashes when git HEAD has moved, and isError=true when the file is missing.

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 core action and usage condition, then adds exclusions and behavioral details in a compact sequence. Despite covering several important behaviors, every sentence contributes necessary selection or invocation information.

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

Completeness5/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 fully explains return values, error behavior, and the drift warning. Together with annotations covering safety and locality, it gives an agent everything needed to invoke and interpret the tool correctly.

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?

The tool takes zero parameters, so there are no parameter semantics to clarify; the baseline for zero parameters is 4. The description does not need to compensate for any parameter documentation gaps.

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 uses specific verbs and resources: it reads the current .vicem/BATON.md handoff document and checks git HEAD drift against .vicem/baton.json. It also distinguishes itself from the sibling tools vicem_create_baton, vicem_rehydrate, and vicem_check_guard.

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

Usage Guidelines5/5

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

It explicitly says to use this first when starting a handed-off session and lists what not to use it for, naming the alternative tool for each excluded action. This leaves no ambiguity about when to select this tool versus its siblings.

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