Skip to main content
Glama
Sign In
Local Repo Automation MCP

Local Repo Automation MCP

by ERSONUMECH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

repository_status

Display a repository's active branch, file changes, and last commit to identify uncommitted work and current position.

Instructions

Show the current branch, porcelain status, and recent commit for a repository.

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

Input Schema

NameRequiredDescriptionDefault
repositoryPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. The verb 'Show' clearly implies a read-only operation with no side effects. It does not mention permissions or any additional behavior, but the action is unambiguous for a status 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?

A single sentence with zero fluff. The key actions are front-loaded, and every word contributes to understanding the tool's purpose.

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 simple tool with one parameter and no output schema, the description covers the essential behavior. It lacks explicit read-only confirmation, but the verb 'Show' is sufficient. No critical information is missing for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only references 'a repository' without explaining the format, required nature, or validation of repositoryPath. The parameter's meaning is minimally implied but not elaborated.

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 clearly states the verb 'Show' and the specific resource: current branch, porcelain status, and recent commit. This distinguishes it from siblings like repository_diff (which shows diffs) and commit_repository (which commits changes).

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 for checking repository state, but it does not explicitly state when to use it vs. alternatives like repository_diff or list_repositories. No exclusions or conditions are provided, leaving the agent to infer context.

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