Skip to main content
Glama

Build Reconstruction Obligation Ledger

build_reconstruction_obligation_ledger
Idempotent

Generate a deterministic reconstruction obligation ledger from authenticated evidence, reviewed obligations, and a manifest; it fails closed on gaps and returns closure digest plus typed diagnostics.

Instructions

Generate the complete deterministic ReconstructionObligationLedger from an authenticated Evidence bundle, reviewed obligations, and an explicit reconstruction manifest. Static candidates remain candidates; duplicate ownership, missing original or reconstruction cases, missing parser/type, weak verifier authority, unenumerated claims, contradictions, dependencies, and residual unknowns fail closed. The inline result carries the full-ledger closure digest and typed per-obligation diagnostics.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "manifest": {
        "bindings": [],
        "contradictions": []
      },
      "evidence_bundle": {
        "records": [],
        "captures": [],
        "unknowns": [],
        "artifacts": [],
        "providers": [],
        "scenarios": [],
        "environments": []
      },
      "reviewed_obligations": []
    },
    "name": "build_reconstruction_obligation_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYes
evidence_bundleYes
reviewed_obligationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructive=false, but the description goes further by enumerating the fail-closed conditions (duplicate ownership, missing cases, missing parser/type, weak verifier authority, unenumerated claims, contradictions, dependencies, residual unknowns) and by stating that static candidates remain candidates. It also discloses what the inline result carries. It stops short of saying how failures surface (error vs diagnostic payload) or what authority is required to build the ledger.

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?

Three sentences, front-loaded with the verb and produced artifact, then failure semantics, then result contents. Dense domain jargon but every clause carries information; no filler or restatement of the title.

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 high-complexity tool with three deeply nested inputs and no output schema, the description covers intent, failure behavior, and a hint at return contents (closure digest and typed per-obligation diagnostics). It leaves unclear whether the ledger is returned inline in full, persisted, or referenced by digest only, which is important for a builder with no output schema.

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?

Top-level schema description coverage is effectively zero, so the description must carry the load; it does name and characterize all three required inputs (authenticated Evidence bundle, reviewed obligations, explicit manifest), which is more than the parameter names alone convey. It adds no detail about expected structure, cross-references between obligations and manifest bindings, or minimal viable inputs, so the compensation is only partial.

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?

The description pairs a specific verb ('Generate') with a named artifact ('complete deterministic ReconstructionObligationLedger') and names its three inputs, so the operation is unambiguous. It does not explicitly contrast itself with nearby siblings such as evaluate_reconstruction_coverage or verify_reconstruction, so an agent must infer the boundary.

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?

Preconditions are implied by naming an 'authenticated Evidence bundle', 'reviewed obligations', and an 'explicit reconstruction manifest', which tells the agent roughly when this tool is applicable. However, there is no explicit when-to-use vs when-not guidance and no routing to alternatives for coverage evaluation or verification.

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