Skip to main content
Glama

git_show

Read-only

Inspect a commit's author, date, message and changed-file summary, or read a file's full content at that commit. Use it to review an old version before restoring it.

Instructions

Show one commit's author, date, message and changed-file summary, or, with path, the full content of one file as it was in that commit. Read-only. Use it to inspect an old version before restoring it with git_restore. For line-by-line changes use git_diff.

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

Input Schema

NameRequiredDescriptionDefault
refYesCommit to show: a hash, "HEAD", "HEAD~2", a tag or a branch name.
pathNoShow this file's content at ref instead of the commit summary. File path relative to the mirror folder, as git_status or git_log prints it, e.g. "ServerScriptService/Main.server.luau".
placeNoTarget place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / path / description
      Added value: +"Show this file's content at ref instead of the commit summary. File path relative to the mirror folder, as git_status or git_log prints it, e.g. \"ServerScriptService/Main.server.luau\"."
    • 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 / ref / description
      Previous value: -"commit hash, HEAD, HEAD~2, tag, branch…"New value: +"Commit to show: a hash, \"HEAD\", \"HEAD~2\", a tag or a branch name."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'Read-only' line is largely redundant with them. However, it adds real behavioral context beyond the annotations by spelling out the two distinct output shapes (commit summary vs. full file content) in a tool with no output schema, which is what an agent needs to predict the response.

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?

Two compact sentences, front-loaded with the primary behavior and its variant, followed by safety and routing hints. No filler or restated title.

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 three-parameter read tool with no output schema, the description covers both modes, the safety profile, and sibling routing, which is nearly everything needed to call it correctly. It does not mention edge cases such as a nonexistent path at that ref or output truncation for very large files, which is a minor remaining gap.

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 coverage is 100%, so ref, path, and place are already fully documented in the schema, including accepted ref forms and the path format. The description's 'with path' phrasing restates the mode switch that the schema's path description already explains, adding little new meaning. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 commit) and enumerates exactly what is returned: author, date, message, changed-file summary. It also names the second mode (with path, full file content at that commit), so the two behaviors are distinguishable at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('inspect an old version before restoring it with git_restore') and an explicit exclusion routing to a named sibling ('For line-by-line changes use git_diff'). An agent can pick between git_show, git_restore, and git_diff without opening any schema.

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