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

io.github.xngg1021/academic-research-kernel

by xngg1021

research_receipt_verify

Verifies an AcademicEvidenceReceipt or LineageReceipt against a strongly typed ReceiptRef, including authorized content payloads, to confirm research evidence integrity and lineage.

Instructions

Verify an AcademicEvidenceReceipt or LineageReceipt against a strongly typed ReceiptRef.

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": {
      "receipt_ref": "<receipt_ref>",
      "receipt_payload": "<receipt_payload>"
    },
    "name": "research_receipt_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
receipt_refYesThe ReceiptRef reference dictionary.
receipt_payloadYesThe full physical receipt payload dictionary to verify.
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?

With no annotations, the description carries the full disclosure burden and largely drops it. It implies a non-mutating check but says nothing about what a failed verification looks like, whether errors are raised or returned, whether verification is deterministic/offline, or what the 10 MiB content cap means for behavior in practice.

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 front-loaded sentence with no filler, naming the operation and both accepted receipt types. It is efficient but borders on under-specification given the tool's role in a verification pipeline.

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?

Parameters are fully documented by the schema, so the input side is covered. However, with no output schema and no annotations, the agent has no idea what a verification result looks like (boolean, diagnostics list, error shape), which is the central thing an agent needs before deciding to call it.

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 baseline is 3. The description adds only the notion that the ReceiptRef must be 'strongly typed' and that the payload is the physical receipt; it says nothing about the optional content_payloads parameter or how content is matched to lineage entity IDs.

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?

Specific verb+resource: 'Verify' applied to two named receipt types (AcademicEvidenceReceipt, LineageReceipt) against a ReceiptRef. This distinguishes it reasonably well within a sibling set dominated by validate/trace tools, though it never explicitly contrasts itself with research_artifact_validate or claim_evidence_validate, so the boundary is inferred rather than stated.

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?

The description gives no when-to-use guidance, no prerequisites (e.g., that verification requires an issued receipt), and no alternatives. An agent must infer from the verb alone that this is a post-hoc integrity check rather than a step in the ingest/validate workflow.

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