Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

getCommitDetails

Read-only

Retrieve commit details: author, date, message, changed files, and optional diff patch. Accepts commit hash and optional file filter.

Instructions

Full commit details: author, date, message, changed files, optional diff patch.

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": {
      "commitHash": "<commitHash>"
    },
    "name": "getCommitDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathNoLimit diff to a single file (absolute or workspace-relative)
commitHashYesFull or abbreviated commit hash
includePatchNoInclude full diff patch. Default: true. Set false for metadata/stats only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Description adds value over annotations by specifying returned fields. However, it does not disclose potential performance impact of including patches on large commits or that it operates on the current repository. Annotations already indicate read-only nature.

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?

Description is concise (one sentence) and front-loaded with key information. Could be slightly more structured but avoids redundancy.

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?

Given no output schema, description lists major output fields. However, it does not specify return format (single object vs. array), nor clarify that it works on the current Git repository. Adequate for a simple retrieval tool.

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?

Input schema has 100% coverage with well-described parameters (commitHash, includePatch, filePath). Description adds minimal extra meaning beyond confirming optional diff patch.

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?

Description clearly states it returns full commit details including author, date, message, changed files, and optional diff patch. This distinguishes it from sibling tools like getGitLog (lists commits) or getDiffBetweenRefs (compares refs).

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 guidance on when to use this tool over alternatives such as getGitLog for listing commits or getDiffBetweenRefs for comparing branches. Lacks context for appropriate use cases.

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