Skip to main content
Glama

Upstream.codes

List commits

list_commits
Read-only

List commits on a branch, tag or commit (default branch when ref is left out), optionally only those touching a path.

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": "list_commits"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
pathNo
repoYesRepository slug.
ownerYesNamespace that owns the repository (user or organization handle).
cursorNonextCursor from a previous page.
perPageNoResults per page (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the default-ref fallback behavior, which is genuinely useful beyond the annotations, but says nothing about result ordering, result shape, or how paging behaves at the edges.

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 dense sentence with the resource first, the default-ref behavior parenthesized inline, and the optional filter last. No filler, nothing that could be cut without losing information.

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 list tool with no output schema, the definition covers resource, scope, defaulting, and filtering, and the remaining parameters are documented in the schema. It is slightly thin on pagination expectations and result ordering, but not deficient for this complexity.

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 67%, with 'ref' and 'path' being the two undocumented parameters — and the description supplies exactly the missing semantics for both (ref is optional and defaults to the default branch; path is an optional filter on touched files). That is meaningful added value over the schema rather than repetition.

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?

Names a specific verb and resource ('List commits') plus the scope (branch, tag or commit) and an optional path filter. An agent can distinguish it from get_commit by verb alone, though the description never explicitly contrasts the two.

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

Usage Guidelines3/5

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

Implicit guidance only: it reveals that omitting 'ref' lists the default branch and that 'path' narrows to commits touching that path, which helps an agent decide how to call it. It never states when to prefer it over siblings like get_commit or compare_refs, and gives no exclusions.

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