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

io.github.xngg1021/academic-research-kernel

by xngg1021

claim_evidence_validate

Validate a ClaimEvidenceGraph snapshot for structural integrity, cycles, and cryptographic receipt bindings, confirming that claims and evidence remain consistent and tamper-evident.

Instructions

Validate the structural integrity, cycles, and cryptographic receipt bindings of a ClaimEvidenceGraph snapshot.

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": {
      "graph": "<graph>"
    },
    "name": "claim_evidence_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphYesClaimEvidenceGraph 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

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It names the aspects checked but does not state whether the operation is read-only, what it returns, how failures are reported, or whether it mutates the snapshot.

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?

One sentence, front-loaded with the verb and object, and no redundant material. It is as concise as the definition can be while still naming the checks.

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?

The core purpose is clear and the schema is fully documented, but there is no output schema and the description does not describe the validation result, severity, or error shape. For a nested validation tool with optional receipts and content payloads, this is a meaningful gap, though the essential operation remains understandable.

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 input schema already defines graph, receipts, and content_payloads. The description adds no parameter-level syntax, format, or constraint details beyond the term 'receipt bindings'; baseline 3 applies for high coverage.

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 gives a specific verb ('Validate') and a precise resource ('ClaimEvidenceGraph snapshot') with concrete checks: structural integrity, cycles, and cryptographic receipt bindings. It is clear what the tool does, but it does not explicitly distinguish itself from nearby validation/trace siblings.

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 guidance on when to use this validator versus claim_evidence_trace or other validation tools, nor any prerequisites or exclusions. The only usage signal is the implicit idea that it is for validation.

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