GravityPort

generation_lineage

Read-only

Read the connected lineage graph around a single generation event to see parent and child IDs plus evidence-bearing relations, clarifying how an AI output was produced.

Instructions

Read the connected generation lineage graph around one generation event, including parent/child IDs and evidence-bearing relations.

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": {
      "generationId": "<generationId>"
    },
    "name": "generation_lineage"
  }
}

Input Schema

Name	Required	Description	Default
`generationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.11Nov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavioral content by saying what the read returns (parent/child IDs, evidence-bearing relations), but it is silent on traversal depth, direction, or size limits for the 'connected graph', which matters for a graph read with no output schema.

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?

A single front-loaded sentence with the resource and the returned content in order of importance, and no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with annotations and no output schema, the description covers the anchor, the scope (graph around it), and the shape of what comes back. The only notable gap is traversal semantics — how far the 'connected' graph extends — which an agent might need before calling.

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 coverage is 0%, so the description must carry the parameter meaning; it partially does by clarifying that the single ID anchors 'one generation event' and that the graph is read around it. It still gives no format or validity detail for generationId beyond that.

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?

States a specific verb ('Read') and a specific resource ('the connected generation lineage graph around one generation event'), and names the payload ('parent/child IDs and evidence-bearing relations'). This distinguishes it from generation_list and generation_record by scoping to one anchor event, though it does not explicitly name those siblings.

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?

Usage is implied by the phrase 'around one generation event', which signals this is the per-event graph lookup rather than a listing tool. However, there is no explicit when-to-use/when-not statement and no named alternative for users who want a flat list or a single record.

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