Skip to main content
Glama

git_health_audit

Audit a local Git repository's health and hygiene via repo-doctor and return a 0–100 score, grade, pillar breakdown, and remediation steps.

Instructions

Déclenche un audit de santé et d'hygiène complet d'un dépôt Git local via repo-doctor (score 0-100, grade, piliers et remédiations)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo_path": "<repo_path>"
    },
    "name": "git_health_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
min_scoreNoScore de passage minimal requis (défaut : 80)
repo_pathYesChemin local du dépôt Git à auditer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool runs a repo-doctor audit and reports score, grade, pillars, and remediations, but it does not explicitly confirm read-only behavior, permissions requirements, or whether the repository is modified in any way.

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 definition is a single front-loaded sentence with no redundant wording. The parenthetical result summary is compact and adds useful scope without making the description bloated.

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

Completeness3/5

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

The tool has only two parameters and no output schema, so the description should cover the key behavioral and return context. It does state the audit output categories, but it omits details such as whether repo-doctor must already be installed, how results are delivered, and whether the operation has any side effects.

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%, so both parameters are already documented in the input schema. The description adds context that the audit score is 0-100, which relates to min_score, but it does not add parameter-specific meaning beyond what the schema provides.

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 description uses a specific verb, 'Déclenche', and names the exact resource: a complete health and hygiene audit of a local Git repository via repo-doctor. It also distinguishes the result set with score 0-100, grade, pillars, and remediations, so the agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

The description implies usage by specifying a local Git repository and repo-doctor, and the sibling tools are unrelated, so no direct alternative is named. However, it does not state explicit when-to-use or when-not-to-use conditions, leaving the agent to infer the context.

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