Skip to main content
Glama

LogNexus Status: Inspect workspace and Git branch state

lognexus_status

Get a read-only snapshot of the current Git branch, repository status, active issue, routing mode, and recommended model tier before choosing a branch, tier, or next action.

Instructions

Inspect the current Git branch, whether the directory is a Git repository, the active issue, the routing mode and the recommended model tier. Use when you need a cheap read-only snapshot before choosing a branch, a tier, or a next action. Not for reading the subtask contract (use lognexus_state_get) or for refreshing the state from Git and GitHub (use lognexus_state_sync).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.6
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

There are no annotations, so the description carries the burden; it discloses a read-only, low-cost snapshot, and it clarifies that refreshing state is delegated to another tool. It does not state anything about output shape or auth, but read-only + cheap + scoped is meaningful behavioral context; without annotations this is strong but not exhaustive.

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?

The description consists of three sentences: what it inspects, when to use it, and when not to use it. The 'what' is front-loaded, and the routing sentence earns its place by preventing misuse of sibling tools.

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?

For a zero-argument status tool, this is nearly complete: it enumerates the data points returned and points elsewhere for anything richer. It stops short of describing the shape or fields of the response (for example, whether the tier is a string, and how 'not a repo' is represented), and there is no output schema to cover that gap.

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

Parameters4/5

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

The tool takes zero parameters, so under the rubric it scores at the baseline of 4. There is no parameter content to describe, and the description correctly focuses on what the tool returns instead of inventing argument semantics.

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?

The definition opens with a specific verb ('Inspect') and then enumerates exactly what is inspected: Git branch, Git-repository status, active issue, routing mode, and recommended model tier. A sibling such as lognexus_state_get or lognexus_state_sync is clearly distinguishable from this tool by that enumeration, so it meets the 5 criteria.

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?

The definition states the trigger for use, 'a cheap read-only snapshot before choosing a branch, a tier, or a next action,' and it names two alternatives for solving adjacent problems: lognexus_state_get for the subtask contract and lognexus_state_sync for refreshing state from Git and GitHub. Both the exclusions and the alternative tools are explicit.

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