Skip to main content
Glama
io.github.xngg1021/academic-research-kernel

io.github.xngg1021/academic-research-kernel

by xngg1021

decision_ledger_validate

Run complete four-gate verification over a Decision Ledger export to confirm integrity, evidence receipts, and claim-evidence consistency before trusting a research decision log.

Instructions

Execute complete four-gate verification over a Decision Ledger export dictionary.

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": {
      "ledger": "<ledger>"
    },
    "name": "decision_ledger_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
ledgerYesDecisionLedger export dictionary.
receiptsNoPhysical receipt registry keyed by receipt ID or payload SHA-256.
content_payloadsNoAuthorized base64 content by lineage entity ID; maximum total 10 MiB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not explain what the four gates check, whether the operation is read-only, what happens on validation failure, or what the tool returns, leaving significant gaps for a validator.

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 description is a single front-loaded sentence with no filler. It is efficient, though its extreme brevity means it omits useful context rather than wasting words.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested object parameters, no annotations, and no output schema, a single sentence is not enough. The description should explain what the four gates verify and what outcome the caller should expect, especially since the return behavior is undocumented elsewhere.

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?

Schema description coverage is 100%, so the schema already documents all three parameters, including the optional receipts and content_payloads with the 10 MiB limit. The description adds only a restatement that ledger is a Decision Ledger export dictionary, so baseline 3 is appropriate.

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 states a specific verb and resource: "Execute complete four-gate verification over a Decision Ledger export dictionary." It is clear what the tool operates on, but it does not distinguish this validation from sibling validators such as claim_evidence_validate or research_artifact_validate.

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 explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The word "complete" hints that it is a full verification pass, but the agent is left to infer when that is appropriate.

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