Skip to main content
Glama

LogNexus Audit: Audit review gate and commit traceability

lognexus_audit

Audit branch commits against the review gate to check commit format, Authored-by trailers, Git Notes coverage, subtask contracts, and author/reviewer separation before merge or PR.

Instructions

Audit the branch commits against the LogNexus review gate: commit format, Authored-by trailer, Git Notes coverage, subtask file contracts, and author/reviewer separation including self-approval detection. Use when you need the pass/fail gate before merging or before opening a pull request. Not for producing the PR narrative (use lognexus_timeline); audit reports violations and never fixes them.

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": {
      "baseBranch": "main"
    },
    "name": "lognexus_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
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"
      +  }
      +]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden; it does state that the tool is non-mutating ('audit reports violations and never fixes them') and what it inspects, which is the key behavioral trait. It leaves unstated whether the check reads from local refs or contacts origin, and how long/heavy it is, so it falls short of fully self-describing for an annotation-free tool.

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?

Three sentences, front-loaded with the action and checks, then usage, then the boundary and the non-fixing guarantee. Every sentence adds distinct information; nothing is restated from the schema or title.

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?

Covers purpose, trigger, exclusion, and the read-only nature of the audit. With no output schema, the description gives only a coarse notion of the result ('pass/fail gate', 'reports violations') without saying whether findings come back as a list, counts, or per-commit detail — a modest gap for a diagnostic tool.

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 there is a single optional parameter whose default and origin fallback are already documented in the schema. The description adds no additional semantics about baseBranch (e.g., what 'origin fallback' means in practice, or effect on which commits are considered), so the baseline 3 applies.

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?

Specific verb (audit) plus a concrete resource (branch commits against the LogNexus review gate), then enumerates the five checks performed: commit format, Authored-by trailer, Git Notes coverage, subtask file contracts, author/reviewer separation. It also explicitly distinguishes itself from lognexus_timeline, so an agent can pick correctly without opening a schema.

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 an explicit trigger ('before merging or before opening a pull request') and an explicit exclusion with the alternative named ('Not for producing the PR narrative (use lognexus_timeline)'). Both when-to-use and when-not-to-use are stated, not inferred.

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