Skip to main content
Glama
Sign In
AgentsID Guard

AgentsID Guard

Official
by AgentsID-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

git_run

Execute git commands under permission control. Read operations (status, log, diff) require read access; write operations (commit, push) require write access.

Instructions

Run a git command. Read operations (status, log, diff) require git.read.. Write operations (commit, push) require git.write..

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": {
      "command": "<command>"
    },
    "name": "git_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesGit subcommand and arguments (e.g., 'status', 'log --oneline -5', 'push origin main')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It mentions permission requirements for read/write operations, which is useful beyond the schema. However, it does not describe output, error handling, or execution context (e.g., working directory).

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?

Two short sentences communicate purpose and permission requirements with zero waste. The description is front-loaded with the primary action and immediately follows with essential authorization context.

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 low-complexity tool with a single parameter, the description covers purpose and access nuances. It omits output format, but for a command runner this is somewhat implicit. Overall, it is nearly complete.

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 coverage is 100% and the parameter description includes examples. The tool description adds no new parameter semantics beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb and resource ('Run a git command'), and the examples clarify scope. It does not explicitly differentiate from sibling tools like shell_run, but the name and description make the purpose clear.

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 provides permission context (read vs write operations) but does not explicitly state when to choose this tool over alternatives such as shell_run. Usage is implied rather than clearly prescribed.

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