Skip to main content
Glama

Show a pull's lineage

lineage
Read-only

List a pull request's parent, ancestors, and child pulls to show what it modifies and what modifies it.

Instructions

List a pull's lineage: the pull it tweaks (parent, and that one's ancestors) and the pulls that tweak it (children).

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": {
      "pull_id": "<pull_id>"
    },
    "name": "lineage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 the safety profile is covered. The description adds the useful fact that results include both ancestors and children, but says nothing about depth limits, whether the ancestor chain is complete, ordering, or result size.

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?

One sentence, front-loaded with the action and resource, with the parenthetical defining the two directions. It is slightly dense but contains no filler or redundancy.

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?

For a one-parameter read tool with no output schema, the description does the essential job of explaining what the returned graph contains. It falls short on the identifier format and on any limits of the lineage traversal, which an agent would need to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter, pull_id, with 0% schema description coverage, so the description must carry the semantic load. It only implies that the id identifies a pull; it never states the expected format (numeric id, UUID, slug, or URL) or whether it must reference a pull that exists.

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 uses a specific verb ("List") and resource ("a pull's lineage") and then defines lineage concretely as the parent chain plus the children. This is clear enough to distinguish it from generic read tools, though it doesn't explicitly contrast with a closely related sibling such as "tweak".

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 only implied: an agent can infer it should call this when it needs ancestry or dependents for a pull. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must reason about fit from the definition alone.

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