Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

git_remote

Read-only

View configured Git remotes and their URLs without altering repository settings, so you can verify where pushes and pulls will be directed.

Instructions

View Git remotes without changing repository settings.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. "Without changing repository settings" largely restates readOnlyHint and adds essentially no new behavior detail such as output shape, ordering, or what happens when no remotes are configured.

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 short sentence with the read-only guarantee front-loaded after the verb and resource. There is no filler or redundancy.

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?

There is no output schema, so the description is the only place an agent could learn what a remote listing returns, and it says nothing about that. For a trivial zero-parameter read tool the safety annotations cover most of the need, leaving this adequate but with a visible gap on return content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a parameterless tool applies. Nothing about the empty schema is contradicted.

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?

"View Git remotes" gives a specific verb plus resource, so an agent can tell this is a read-only listing of configured remotes rather than a status/diff/branch call. It stops short of saying what a remote listing contains (names, fetch/push URLs), so it is clear but not fully concrete.

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 "without changing repository settings" clause implies this is the safe read path versus any mutating Git operation, but no when-to-use condition or explicit alternative is named. With zero parameters there is little to disambiguate, so implied usage is tolerable but not instructive.

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