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

io.github.xngg1021/academic-research-kernel

by xngg1021

research_lineage_trace

Trace an entity's backward provenance ancestry in a LineageGraph snapshot to identify upstream source data, activities, and dependencies for reproducibility audits.

Instructions

Trace backward provenance ancestry for a specified entity within a LineageGraph 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": {
      "lineage_graph": "<lineage_graph>",
      "target_entity_id": "<target_entity_id>"
    },
    "name": "research_lineage_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineage_graphYesExported LineageGraph dictionary.
target_entity_idYesThe entity ID to trace upstream lineage from.

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 says the trace is backward and operates within a snapshot, but it does not disclose read-only behavior, return format, cycle handling, depth limits, or error behavior for a complex nested graph operation.

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 concise, though the phrase 'backward provenance ancestry' is somewhat jargon-heavy and the definition remains terse for a complex graph tool.

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 a rich nested LineageGraph object and has no output schema, yet the description does not explain the return value or traversal behavior. For a complex provenance-tracing operation, this leaves important context missing.

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 both parameters. The description adds only the notions of backward tracing and snapshot scope, which are useful but do not add much beyond the structured parameter definitions.

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: tracing backward provenance ancestry for a specified entity within a LineageGraph snapshot. It is clear what the tool does, but it does not explicitly distinguish itself from sibling trace tools such as claim_evidence_trace or decision_trace.

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 exclusions, and no alternatives. It implies the tool is for lineage tracing but does not tell an agent when to choose it over other trace or validation tools.

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