Skip to main content
Glama

mnemon_branch_lineage

Inspect the visual DAG ancestry and branch lineage tree for CoW database branches using a tenant ID.

Instructions

Inspect the visual DAG ancestry and branch lineage tree of CoW database branches.

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": {
      "tenant_id": "<tenant_id>"
    },
    "name": "mnemon_branch_lineage"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it never states explicitly that the operation is read-only, whether it needs elevated permissions, how expensive it is to run on large DAGs, or what 'visual' means as an output (ASCII art versus structured JSON). The word 'Inspect' hints at a read operation, but the description leaves that operation undocumented.

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?

This is a single front-loaded sentence with no filler or redundancy. It is perhaps slightly too terse, but nothing needs trimming.

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?

With one required parameter, no annotations, and no output schema, the description should tell the agent what the tool returns and how deep the lineage goes. It gestures at a 'visual' DAG but never specifies the response shape or any limits, which leaves a real gap for an agent that is composing a call it cannot open an output schema to check.

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?

There is only one parameter, tenant_id, and the schema description coverage is 100%, so the schema already explains it fully. The description adds no information about the identifier's format or scoping. With full coverage on a single parameter, the baseline score of 3 is appropriate.

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 pair: inspecting the branch lineage tree (a DAG of ancestry) for CoW database branches. That is clearly distinct from mutating siblings like mnemon_create_branch or mnemon_reset_branch, though it does not differentiate itself from read-oriented siblings such as mnemon_diff_branch or mnemon_list_snapshots.

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 contains no when-to-use guidance, no prerequisites, and no named alternatives. Because its name contains the word 'lineage', an agent can infer that the tool is for ancestry analysis, but nothing states whether to prefer this tool over mnemon_diff_branch or mnemon_time_travel when tracing branch history.

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

Deploy Server

Other Tools