Skip to main content
Glama

GitPicker

get_commits

查看 GitHub 仓库某个分支的提交历史(sha、提交信息、作者、日期)。当用户想了解仓库最近改动、开发活跃度或某次提交内容时使用。branch 缺省自动用默认分支,按时间倒序 25 条/页。

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>"
    },
    "name": "get_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo页码,从 1 开始,默认 1
repoYes仓库名
ownerYes仓库属主
branchNo分支名,缺省用默认分支

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and delivers real behavioral detail: branch 缺省自动用默认分支, results are 按时间倒序, and page size is fixed at 25 条/页. What it does not disclose is the safety/auth profile — whether private repos are reachable, what permissions or token scopes are needed, or whether pagination has an end condition — which for an unannotated tool leaves a meaningful 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?

Three compact sentences with zero filler: capability and return fields first, then usage triggers, then defaults/paging. The most decision-relevant information is front-loaded and nothing is repeated.

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 four-parameter read tool with no output schema, the description covers what is returned, how pages are sized, ordering, and the branch default — enough to invoke it correctly. It omits any mention of auth requirements or how to detect the last page, which keeps it from a 5.

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%, so all four parameters are already documented in the schema itself, and the description's only added semantics are the default-branch fallback (already in the branch schema description) and the 25-per-page size that gives page its units. That is marginal value beyond structured data, 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+resource (查看提交历史) and enumerates the returned fields (sha、提交信息、作者、日期), so an agent knows exactly what comes back. It stops short of naming a sibling like get_issues or list_branches as the contrast case, so differentiation is by inference from the resource noun rather than explicit routing.

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

Usage Guidelines4/5

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

It gives three concrete usage triggers: 了解仓库最近改动、开发活跃度、某次提交内容. That is clear positive guidance with no exclusions and no named alternatives, so it earns a 4 rather than a 5 — an agent is never told when to prefer another tool instead.

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