Skip to main content
Glama

LogNexus Timeline: Generate PR Journey Timeline

lognexus_timeline

Reconstruct a branch's journey timeline with enriched commits, Git Notes, subtask IDs, tiers, and trailers; render as a Markdown table, JSON, or PR body draft for PR descriptions and subtask review.

Instructions

Reconstruct the branch Journey Timeline against a base branch: commit list enriched with Git Notes, subtask IDs, tiers and Authored-by/Reviewed-by trailers, rendered as a Markdown table, JSON or a PR body draft. Use when preparing a pull request description or reviewing the subtask sequence of a branch. Not for judging compliance (use lognexus_audit, which reports violations rather than a narrative).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "format": "pr-body",
      "baseBranch": "main"
    },
    "name": "lognexus_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format. Defaults to 'table'.
baseBranchNoBase branch to compare against. Defaults to 'main' with origin fallback.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.6
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "baseBranch": "main",
      +    "format": "pr-body"
      +  }
      +]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it names the data sources (Git Notes, subtask IDs, tiers, Authored-by/Reviewed-by trailers) and the three output renderings, which imply a read-only synthesis operation. It stops short of stating repository/auth prerequisites, failure behavior for an unknown base branch, or whether it mutates any state.

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 purpose and output surface are front-loaded in the first sentence, followed by one usage sentence and one exclusion sentence; every sentence earns its place. The opening sentence is dense and slightly overloaded with the enrichment list, which is up to 20 words of detail before the agent knows the output formats.

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, and the description compensates by describing the three output forms and the enriched fields. For a zero-required-parameter read tool this is close to complete; only the environment/prerequisite context (needing a git repo with the base branch present) is left implicit.

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%, so the baseline is 3. The description's mention of 'Markdown table, JSON or a PR body draft' loosely maps to the format enum and 'against a base branch' mirrors baseBranch, but it adds no format-specific behavior (e.g., what the PR body draft contains versus the table) beyond the schema.

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?

States a specific verb ('Reconstruct') and resource ('branch Journey Timeline against a base branch') and enumerates what the output contains (commits enriched with Git Notes, subtask IDs, tiers, trailers) and its renderings. It explicitly distinguishes itself from lognexus_audit, so an agent can separate the two without inspecting schemas.

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

Usage Guidelines5/5

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

Gives concrete trigger conditions ('preparing a pull request description', 'reviewing the subtask sequence of a branch') and an explicit exclusion with the correct alternative ('Not for judging compliance (use lognexus_audit, which reports violations rather than a narrative)'). Both when-to-use and when-not-to-use are present.

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