Skip to main content
Glama
Sign In
ForgeGuard MCP

ForgeGuard MCP

by KatoteshiKuka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

git_status

Get concise file-change state for a registered project by running git status --short directly, avoiding shell invocation.

Instructions

Run git status --short inside a registered project without invoking a shell.

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": {
      "projectId": "<projectId>"
    },
    "name": "git_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0-alpha.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool does not invoke a shell, which is a meaningful execution trait, and specifies the short-format status output. It does not detail error behavior, but git status is a standard read-only operation and the command itself implies its behavior.

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, front-loaded sentence states the action, scope, and a key behavioral distinction with no wasted words. It is concise without losing necessary information.

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 one-parameter read-only Git status tool, the description plus schema is nearly sufficient for correct invocation. It lacks explicit return-format details and error handling, but '--short' already communicates the expected output style and the schema supplies the only required input.

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 schema has 0% description coverage, so the description must provide parameter meaning. It supplies the semantic anchor 'inside a registered project,' which maps to projectId, but it does not explicitly state that projectId is the identifier of the registered project or explain the UUID constraint. With only one parameter, the mapping is still inferable.

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 names a specific command and resource: 'Run git status --short inside a registered project.' This clearly states what the tool does and distinguishes it from related tools like git_diff or process_run.

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?

It gives clear usage context: the command must run inside a registered project, and the tool is specifically a shell-free way to get git status. It does not explicitly name alternative tools or when not to use it, but the context is sufficient for an agent to choose it over running a shell command.

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