Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Commit all config changes

git_git_commit_all

Stages and commits all changes in the Home Assistant config directory to create a checkpoint before risky edits; skips commit when the working tree is clean.

Instructions

Stage and commit every change in the HA config directory.

Calls _repo(), stages everything with git add -A, and commits message unless nothing is dirty, in which case no commit is made.

Use when: creating a checkpoint before a risky change to /config. Not for: writing one file and checkpointing it in a single call — use git_safe_write_with_checkpoint. Returns: dict {"status": "committed", "sha", "message"}, or {"status": "nothing_to_commit"} when the working tree is clean. Errors: raises RuntimeError (from _repo()) when gitpython is not installed or no git repo exists yet — run git_git_init_config first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesCommit message describing this checkpoint or change.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.1
    • addedInput schema / properties / message / description
      Added value: +"Commit message describing this checkpoint or change."
  2. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, but the description adds substantial behavioral context: it performs git add -A, skips the commit when nothing is dirty, returns specific status dictionaries, and raises RuntimeError when gitpython is missing or no repo exists. This goes well beyond structured annotations.

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 is front-loaded with the core action, then structured into when-to-use, when-not-to-use, return shape, and error conditions. Every sentence earns its place and directly helps an agent invoke the tool correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single required parameter, annotations covering safety hints, a 100% schema description, and an existing output schema, the description still supplies the missing operational context: no-op behavior, prerequisite initialization, and specific error conditions. Nothing material is missing.

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 description coverage is 100% and the single message parameter is already documented in the schema. The description repeats that message is committed but adds no syntax, format, or validation detail beyond the schema, so the baseline of 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?

States a specific verb and resource: stage and commit every change in the HA config directory. It distinguishes itself from the closely related git_safe_write_with_checkpoint by explaining that sibling handles writing one file and checkpointing in a single call.

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?

Explicitly gives when to use it (creating a checkpoint before a risky change to /config) and when not to use it (writing one file and checkpointing in a single call, directing to git_safe_write_with_checkpoint). The prerequisite git_git_init_config is also called out for the error case.

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