Skip to main content
Glama

Upstream.codes

Get commit

get_commit
Read-only

Read a commit: message, authors, parents and changed files with patches.

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": {
      "owner": "<owner>",
      "repo": "<repo>",
      "ref": "<ref>"
    },
    "name": "get_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesCommit SHA, branch or tag.
repoYesRepository slug.
ownerYesNamespace that owns the repository (user or organization handle).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered. The description adds genuine value beyond that by disclosing the return shape (message, authors, parents, files with patches), which matters because there is no output schema. It does not mention patch truncation for large files or handling of merge commits, which is the only remaining behavioral gap.

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 the verb and resource first and the returned fields after; every clause carries information and there is no filler.

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, describing the returned fields fills the most important gap and lets an agent decide whether it needs patches or just the message. Only edge cases like patch truncation or very large commits are left unaddressed.

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%, and the schema already explains that 'ref' accepts a commit SHA, branch, or tag, plus the owner/repo semantics. The description adds no additional parameter meaning, so the baseline 3 applies.

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 uses a specific verb plus resource ('Read a commit') and enumerates exactly what the payload contains: message, authors, parents, and changed files with patches. It clearly distinguishes reading a single commit from list operations, though it does not name a sibling such as list_commits for discovery.

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?

There is no when-to-use or when-not-to-use guidance; nothing tells the agent to call list_commits first to resolve a SHA, or how this differs from compare_refs or get_change_request_diff. The only implied usage comes from the phrase 'Read a commit' in the purpose sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources