Skip to main content
Glama
Sign In
LocalForge

LocalForge

by tanskong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

git_show

Read-onlyIdempotent

Display one Git revision with bounded patch output for a given repository path and revision. Inspect commit changes without loading unlimited diff data.

Instructions

Show one Git revision with bounded patch output.

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": {
      "path": "<path>",
      "revision": "<revision>"
    },
    "name": "git_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds 'bounded patch output', which is useful behavioral context, but 'bounded' is never quantified (no truncation limit or pagination behavior), leaving the added value incomplete.

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 with no filler; the core operation and its output constraint are stated immediately.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, with 0% schema coverage and an unquantified 'bounded' claim, the definition leaves an agent without enough detail to invoke the tool confidently.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters. The description loosely implies the 'revision' argument but says nothing about 'path' (repository root? file path?) or what revision formats are accepted, so the two required parameters remain ambiguous.

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 (Show) and resource (one Git revision) with a scope qualifier (bounded patch output). It distinguishes itself from git_log/git_diff by implying a single-revision view, though it never explicitly names those siblings.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The word 'one' hints at single-revision scope, but there is no signal about when to prefer git_show over git_diff, git_log, or read_file.

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