Skip to main content
Glama
Sign In
Code MCP Server

Code MCP Server

by agentics-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

git_status

Check the status of a Git repository, including working tree changes and staged files. Specify the repository path to get a summary of modifications, untracked files, and branch information.

Instructions

Get git repository status

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "git_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoRepository path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, return format, or performance implications. Minimal information beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise and front-loaded, consisting of a single phrase. It could be slightly expanded without being verbose, but it is efficient.

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?

For a simple status tool with one parameter and no output schema, the description is adequate but does not explain what the return value looks like or how to interpret it. Slightly incomplete for an agent unfamiliar with git.

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?

The sole parameter 'cwd' is fully described in the schema as 'Repository path', achieving 100% coverage. The description adds no additional meaning beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get git repository status', which clearly identifies the action (get) and resource (git repository status). It distinguishes from sibling tools like git_diff, git_log, etc., though could be more specific about what 'status' includes.

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

Usage Guidelines2/5

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

No guidance provided on when to use this tool versus alternatives like git_diff or git_log. The description lacks any context about the typical use case or prerequisites.

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