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

io.github.xngg1021/academic-research-kernel

by xngg1021

claim_evidence_trace

Trace supporting and refuting evidence anchors plus attached receipts for a specified claim ID to expose claim-evidence provenance and verification paths.

Instructions

Trace all supporting and refuting evidence anchors and attached receipts for a given claim.

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>",
      "claim_id": "<claim_id>"
    },
    "name": "claim_evidence_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphYesClaimEvidenceGraph export dictionary.
claim_idYesTarget claim identifier to trace.
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.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose something useful: the result spans both supporting and refuting anchors plus attached receipts, which is a real content trait beyond the schema. However it says nothing about side effects (read-only vs mutation), permission requirements for the content payloads, the 10 MiB limit, or how missing/unauthorized receipts 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 front-loaded sentence with zero filler, and the core object of the trace is stated first. It is efficient, though perhaps terse given the nested-object parameters.

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 tool takes nested objects and has no output schema and no annotations, so the description should have conveyed what a trace returns and any safety profile. It hints at the return composition but leaves the shape and constraints entirely to the 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?

Schema description coverage is 100%, so all four parameters are already documented, making 3 the baseline. The description adds only the implication that the optional receipts registry feeds 'attached receipts'; it says nothing extra about graph, claim_id, or content_payloads semantics.

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 names a specific verb and resource: tracing supporting and refuting evidence anchors plus attached receipts for a given claim. That scope is precise enough to act on, though it never distinguishes itself from near-siblings such as claim_evidence_validate or research_receipt_verify.

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?

The phrase 'for a given claim' implies the operating context, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling trace/validate tools. An agent must infer the routing decision from the name alone.

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