git-remote-mcp

git_config

Read or write repository git configuration: get a key's value when none is provided, set a value, or unset a key in a local repo.

Instructions

Read or write repository git configuration.

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

Input Schema

Name	Required	Description
`cwd`	No	Optional local working directory or repository path.
`name`	Yes	Config key.
`unset`	No	Unset this config key.
`value`	No	Optional value. When omitted, reads the key.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description fully carries the behavioral burden, yet it discloses almost nothing beyond the verb pair. It does not say that writes mutate repository state, that unset removes a key (potentially destructive), which scope (local/global/system) is affected, or that the tool returns the value on read.

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?

A single front-loaded sentence with no wasted words. It is efficient, though arguably too terse for a tool that both reads and mutates configuration.

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

Completeness2/5

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

For a dual-mode read/write tool with no annotations and no output schema, an agent is left guessing about return values on read and side effects on write/unset. The description should indicate the response shape and the scope of modification but does neither.

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 all four parameters are already documented in the schema, which sets the baseline at 3. The description's 'read or write' phrasing reinforces the value-omitted-means-read behavior, but adds no syntax, format, or scope details beyond the schema.

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 gives a specific verb pair (read or write) and a clear resource (repository git configuration), which is enough to distinguish it from siblings like git_status or git_branch. It lacks any explicit differentiation from other config-like tools, but 'git configuration' is self-evidently unique in this sibling set.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites such as whether a repository must exist or whether the target is local vs global config. The read/write distinction is implied only by the schema's value parameter, not stated as a usage rule.

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