Skip to main content
Glama

GetAssetLineage

Read an asset's lineage as a graph, across every source tool (not only Midjourney): its ancestors and descendants as nodes and edges. Returns {schema_version, asset_h, scope, nodes[], edges[], annotations[], truncated}. Each node has source_tool and tools[] (tool, role, attribution_source) and branch_decision (null = none recorded). Each edge has parent, child, relationship_type, derivation_kind and: state (visible by default; with include_hidden also disputed = sources disagree, not_live = no active assertion), assertion_sources (who currently affirms the edge: extracted = read from the file, user_asserted = a person, client_asserted = an integration or client), match_method (how the parent was identified, e.g. content_hash, mj_job_id, c2pa_ingredient, filename, declared), disagreement and legacy_unasserted. With include_hidden each edge also lists every source's position. annotations are non-lineage links (ReferenceFor, ComponentOf, AlternativeTo) one hop from a returned node; they are never walked. scope "lineage" (default) = ancestors up and descendants down; "family" = the whole connected component, so siblings such as Midjourney grid images appear. truncated is true when max_depth or max_nodes cut the walk short. An unknown, other-tenant or hidden asset returns the empty graph. GetMidjourneyEvolutionChain remains for Midjourney parameter diffs.

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": {
      "asset_h": "<asset_h>"
    },
    "name": "GetAssetLineage"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo"lineage" = ancestors and descendants (default); "family" = the whole connected lineage componentlineage
asset_hYesThe Asset Hash (SHA-1) of the focal asset
max_depthNoMaximum hops to walk (default 10, max 50)
max_nodesNoMaximum nodes to return (default 500, max 2000)
include_hiddenNoAlso return disputed and not_live edges with every source position (evidence view). Default false: only visible edges.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral load and does so well: it enumerates return fields, explains the three edge states, who asserts an edge (extracted/user_asserted/client_asserted), match_method values, that annotations are never walked, that unknown/other-tenant/hidden assets yield an empty graph, and when truncated fires. The main omission is any auth/permission or cost/latency context around a potentially large graph walk. Note the anchor's calibration bands make a 5 appropriate only for fully covered cases - this is close but omits permission and performance context.

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?

Front-loaded with purpose, then return shape, then per-field meaning, then closed with truncation, empty-graph behavior and the sibling handoff - a sensible ordering. It is a single dense block with heavy parenthetical nesting, which costs some scannability, but essentially no sentence is filler.

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?

No output schema exists, so the description must describe the return payload, and it does: field-by-field for nodes and edges plus the annotations array. Combined with full schema coverage for inputs, an agent has what it needs to call this correctly and interpret the result; only auth and performance context are absent.

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 100% and every parameter already carries a description, so the schema does the heavy lifting; the description mostly restates scope and include_hidden. It does add semantics the schema lacks - that include_hidden is an "evidence view" returning per-source positions and disputed/not_live edges, and that max_depth/max_nodes drive the truncated flag - which lifts it to the baseline-plus level rather than above it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read an asset's lineage as a graph, across every source tool" gives a specific verb plus resource and immediately scopes it beyond Midjourney, which is the one thing an agent might otherwise confuse with GetMidjourneyEvolutionChain. It also states the return envelope up front, so the tool's identity is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It defines the two modes precisely ("lineage" = ancestors up and descendants down vs "family" = whole connected component, with Midjourney grid siblings called out) and explicitly routes Midjourney parameter-diff work to GetMidjourneyEvolutionChain. What it does not do is state when not to reach for this tool at all (e.g., use GetAssetDetails for metadata), so guidance is strong but not complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources