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

io.github.xngg1021/academic-research-kernel

by xngg1021

research_artifact_validate

Validate a research artifact envelope against its schema and verify its cryptographic payload SHA-256 without side effects, ensuring data integrity before use.

Instructions

Validate a ResearchArtifactEnvelope against its schema and verify its cryptographic payload SHA-256 without side effects.

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": {
      "envelope": "<envelope>"
    },
    "name": "research_artifact_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
bindingsNo
envelopeYesThe ResearchArtifactEnvelope dictionary to validate.
receiptsNoOptional physical receipt registry required to replay receipt-backed CEG or Ledger snapshots.
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
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add the key behavioral fact that the call is side-effect free and that both structural and cryptographic checks occur, which is genuinely useful. However, it says nothing about what happens on validation failure, whether failures return partial diagnostics, how receipts or content_payloads affect the outcome, or how large/complex envelopes are handled.

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?

A single well-packed sentence, front-loaded with the primary action (validate) and carrying the safety claim at the end. It is efficient with no filler, though the density means several important details are compressed away rather than organized for the reader.

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?

The tool takes five parameters with nested objects, only one required, and has no annotations or output schema to lean on. For that complexity the description is too thin: it does not clarify the roles of state, bindings, receipts, or content_payloads, nor describe the validation result an agent would need in order to act on it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, with 'state' and 'bindings' undocumented in both schema and description, and the description never explains why those inputs exist or how they alter validation. It gestures at the payload hash but does not connect that to the content_payloads parameter (base64, 10 MiB cap) or to the optional receipts registry, so it adds little meaning beyond the schema.

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 specific verbs and a concrete resource: schema validation of a ResearchArtifactEnvelope plus SHA-256 verification of its payload. It is clear what the tool does, but it never distinguishes itself from validation siblings such as claim_evidence_validate, decision_ledger_validate, or research_receipt_verify, leaving the agent to infer which validator applies to which artifact type.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. An agent cannot tell from this text whether it should call this before ingest, after receipt verification, or as a standalone pre-flight check, nor whether it substitutes for the sibling validators.

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