Skip to main content
Glama

vicem_rehydrate

Read-onlyIdempotent

Restores secret-redacted source code for a skeletonized function, method, or class from the ledger, replacing { ... } placeholders so you can inspect or edit symbols listed in the baton.

Instructions

Restores the exact, secret-redacted source code of a skeletonized function, method, or class from .vicem/ledger.json so you never write { ... } placeholders. Use after vicem_read_baton whenever you need to inspect or edit a symbol listed in .vicem/BATON.md Section 6 (Diet Ledger); do not use to read the full baton (vicem_read_baton), build a baton (vicem_create_baton), or check diff safety (vicem_check_guard). Parameter semantics: file_path (repo-relative POSIX path validated against path traversal) and symbol_name must match a ledger entry (camelCase filePath/symbolName aliases also accepted). Read-only lookup (no auth, rate limits, or disk writes): returns the redacted source code (isError=false), prepending a "// ⚠️ [STALENESS DRIFT WARNING]" comment if git HEAD or the on-disk file changed since snapshot. If the symbol is missing or was not skeletonized, returns isError=true with a not-found message so you can read the file directly.

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": {
      "file_path": "<file_path>",
      "symbol_name": "<symbol_name>"
    },
    "name": "vicem_rehydrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesRepository-relative POSIX file path as listed in .vicem/BATON.md Section 6 (e.g., "src/auth.ts" or "vicem.mjs").
symbol_nameYesExact function, method, or class name to restore from .vicem/ledger.json (or comma-separated names like "parseCFamily,classifyCBlockHeader" for batch rehydration).
include_calleesNoWhen true, also restores 1-hop same-file functions called by symbol_name in a single round-trip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / include_callees
      Added value: +{
      +  "default": false,
      +  "description": "When true, also restores 1-hop same-file functions called by symbol_name in a single round-trip.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / symbol_name / description
      Previous value: -"Exact function, method, or class name to restore from .vicem/ledger.json (e.g., \"verifyJwt\" or \"parseCFamily\")."New value: +"Exact function, method, or class name to restore from .vicem/ledger.json (or comma-separated names like \"parseCFamily,classifyCBlockHeader\" for batch rehydration)."
  2. Changed3 schema fields changedv1.1.6
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / file_path / description
      Previous value: -"Relative file path (e.g. src/auth.ts)"New value: +"Repository-relative POSIX file path as listed in .vicem/BATON.md Section 6 (e.g., \"src/auth.ts\" or \"vicem.mjs\")."
    • changedInput schema / properties / symbol_name / description
      Previous value: -"Function, method, or class name (e.g. verifyJwt)"New value: +"Exact function, method, or class name to restore from .vicem/ledger.json (e.g., \"verifyJwt\" or \"parseCFamily\")."
  3. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations' readOnlyHint/idempotentHint, it discloses the operational profile (no auth, no rate limits, no disk writes), the return contract (redacted source with isError=false), the staleness drift warning prepended when git HEAD or the on-disk file changed, and the failure mode (isError=true not-found, with the recommended fallback of reading the file directly). This is well past what the annotations already cover.

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?

Purpose and scope are front-loaded and the sibling exclusions follow immediately, so the agent can stop reading early. The final sentence is dense and multi-clause (return value, staleness comment, error path packed together), which costs a point on scannability but every clause carries real 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?

With no output schema, the description carries the return-value burden itself and does so — success shape, staleness annotation, and error shape are all stated. For a 3-parameter read-only lookup, nothing an agent needs in order to call it correctly or interpret the result is missing.

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 100%, so the baseline is 3; the description earns an extra point by adding constraints the schema omits — path-traversal validation of file_path and acceptance of camelCase filePath/symbolName aliases. It does not mention the include_callees batch option, but the schema documents that fully.

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 resource ('Restores the exact, secret-redacted source code of a skeletonized function, method, or class from .vicem/ledger.json') plus the problem it solves ('so you never write { ... } placeholders'). It is immediately distinguishable from the three siblings, which are named explicitly.

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?

Gives an explicit sequencing rule ('Use after vicem_read_baton') and an explicit exclusion list naming each alternative and its purpose: vicem_read_baton for the full baton, vicem_create_baton for building, vicem_check_guard for diff safety. The triggering condition ('whenever you need to inspect or edit a symbol listed in Section 6 (Diet Ledger)') is concrete.

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