Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List config git commits

git_git_log
Read-onlyIdempotent

List recent commits in the Home Assistant configuration git repository, returning SHA, message, author, and date to review changes before rollback or diff.

Instructions

List recent commits in the HA config git repository.

Calls _repo() and returns up to limit commits from repo.iter_commits, most recent first, with short SHA, message, author name and ISO commit date.

Use when: reviewing recent config changes before a rollback or diff. Returns: list[dict] {"sha", "message", "author", "date"}. Errors: raises RuntimeError (from _repo()) when gitpython is not installed or no git repo exists yet — run git_git_init_config first. Limits: limit caps the number of commits returned; no further pagination is offered.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of commits to return, most recent first. Defaults to 20.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of commits to return, most recent first. Defaults to 20."
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds valuable context beyond that: the exact return shape and the RuntimeError from `_repo()` when gitpython is missing or no repo exists, plus the absence of pagination. This is genuinely additive despite the annotation coverage.

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?

Front-loads the purpose, then organizes the rest into labeled sections (Use when, Returns, Errors, Limits) with no wasted sentences. Every line carries actionable information for the caller.

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?

Given one simple optional parameter, an output schema already present, and rich annotations, the description is complete: it covers purpose, usage, return shape, errors, and limits. It could mention whether the repo is expected to be already initialized beyond the init hint, but nothing essential is missing.

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?

Schema coverage is 100% and the single parameter is well documented there. The description reinforces that `limit` caps the number of commits returned, adds the important constraint that no further pagination is offered, and confirms most-recent-first ordering, which is more than the schema states.

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 (list) and resource (recent commits in the HA config git repository), and the title plus internal call to `_repo()` distinguishes it from siblings like git_git_status or git_git_diff. An agent can immediately tell this reads commit history rather than changing files.

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

Usage Guidelines4/5

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

Provides an explicit 'Use when' cue (reviewing recent config changes before a rollback or diff) and names the prerequisite tool (run `git_git_init_config` first). It doesn't name an alternative sibling for the same job, but the preconditions are clear.

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