Skip to main content
Glama

git_remote

List or add git remotes for a place's mirror repo, so git_push can keep an off-machine copy such as a private GitHub repo. Add requires a name and URL.

Instructions

List the git remotes of a place's mirror repo, or add one. Adding a remote such as a private GitHub repo lets git_push keep a copy off this machine. Adding is blocked in read-only mode and fails if the name already exists.

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_remote"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoRemote URL for add, e.g. https://github.com/you/my-place.git.
nameNoRemote name for add, usually "origin".
placeNoTarget place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place.
actionNo"list" (default) shows remotes; "add" needs name and url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / action / description
      Added value: +"\"list\" (default) shows remotes; \"add\" needs name and url."
    • changedInput schema / properties / name / description
      Previous value: -"remote name, e.g. 'origin'"New value: +"Remote name for add, usually \"origin\"."
    • changedInput schema / properties / place / description
      Previous value: -"Target place (PlaceId or project name); defaults to the bound/sole place"New value: +"Target place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place."
    • changedInput schema / properties / url / description
      Previous value: -"remote URL, e.g. a GitHub repo"New value: +"Remote URL for add, e.g. https://github.com/you/my-place.git."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false; the description adds genuine context beyond that by stating add is blocked in read-only mode and fails on a duplicate name, which explains the non-idempotent flag. It does not address authentication for private remotes or whether remote URLs are validated, and it leaves the list path's behavior unqualified. Useful added behavior, but not a full picture of a mutation with potential network auth needs.

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?

Three short sentences, front-loaded with the dual-mode purpose, then the motivating use case, then the failure conditions. No filler or redundant restatement of the name or schema.

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 four-parameter, dual-mode tool with no output schema, the description covers both modes, the mode-dependent requirements, and the two blocking conditions an agent must anticipate. It is slightly short on what the list mode returns or how remotes are formatted, but the schema covers parameter detail and nothing critical is missing.

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 the schema already documents place, name, url, and the list/add enum, making 3 the baseline. The description reinforces the mode-dependent requirement ('add needs name and url') and gives a realistic URL example context ('a private GitHub repo'), but adds no syntax or defaulting information beyond what the schema states.

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?

States a specific verb plus resource: 'List the git remotes of a place's mirror repo, or add one.' Both modes are named up front and the scope ('place's mirror repo') is explicit, which separates it from sibling git tools like git_commit or git_log. It only partially differentiates from git_push, and only by explaining what adding a remote enables for push.

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?

Gives a concrete reason to use the add mode: a private GitHub remote lets git_push keep an off-machine copy, which tells the agent when this tool is the right precursor to a push. It does not name any alternative for listing remotes or say when to skip this tool, so there is clear context but no exclusions.

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