Skip to main content
Glama
Sign In
Secure Git MCP

Secure Git MCP

by IvanAbramovichWork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

git_show

Read-onlyIdempotent

Inspect a Git commit or commit:path while blocking raw blob/tree access. Omit repo_path to use configured repository; results follow project policy.

Instructions

Show a commit or commit:path; raw blobs/trees are forbidden. Omit repo_path to use the configured repository. Results and operations are restricted according to project policy.

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

Input Schema

NameRequiredDescriptionDefault
revisionYes
repo_pathNoOptional repository root. Omit to use the server's fixed repository. An explicit path must identify that same repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.10.19

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent, read-only operation. The description adds useful behavioral context by noting that raw blobs/trees are forbidden and that results are restricted by project policy, though the policy restriction remains vague.

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?

The description is short and front-loads the core purpose. The policy sentence is somewhat boilerplate, but the overall text is compact and contains little waste.

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 simple read-only tool with rich annotations and no output schema, the description provides enough to call it correctly: valid revision forms, repo_path handling, and key restrictions. It does not describe the return shape, but that is a minor gap for a familiar git show operation.

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?

Schema coverage is only 50%, and the revision parameter lacks a schema description, but the description compensates by explaining that revision can be a commit or commit:path. It also clarifies repo_path behavior, reinforcing the schema's own description.

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 clearly states the verb (Show) and the resources (a commit or commit:path), and it explicitly excludes raw blobs/trees. It does not directly distinguish this tool from siblings such as git_diff_revisions or git_log, but the core purpose is unambiguous.

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?

It gives invocation constraints such as omitting repo_path and forbidding raw blobs/trees, but it does not explain when to use this tool instead of alternatives like git_log, git_diff_revisions, or git_blame. Selection guidance is largely left to inference.

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