Skip to main content
Glama
Sign In
CNB Remote MCP

CNB Remote MCP

by htazq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List commits

repo_commits_list
Read-onlyIdempotent

Lists repository commit history, optionally starting from a branch or commit, and filters by author, date range, and pagination.

Instructions

List commit history, optionally starting from a commit-ish.

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": {
      "repo": "<repo>"
    },
    "name": "repo_commits_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
shaNoStart from this branch/commit
pageNoPage number, starting at 1
repoYesRepository path, e.g. "owner/repo" or "group/subgroup/repo"
sinceNoISO 8601 start time
untilNoISO 8601 end time
authorNoFilter by author username
page_sizeNoItems per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld behavior. The description adds essentially no behavioral context beyond that profile: it does not state ordering, pagination behavior, whether all branches are included, or any rate/auth considerations.

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?

It is a single, front-loaded sentence with no wasted words. The purpose is stated immediately and the optional starting point is appended efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 rich annotations and full schema coverage, the definition is minimally adequate. However, it omits sibling differentiation and any note about result ordering or pagination semantics, which would matter to an agent selecting and invoking the tool correctly.

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 the schema already documents all seven parameters, including sha, page, since, until, author, and page_size. The description's 'commit-ish' phrasing slightly broadens the sha concept but adds no real syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 states a specific verb and resource: 'List commit history', with the optional start point. It is clear what the tool does, but it does not distinguish itself from siblings such as pr_commits or repo_commit_get, leaving the agent to infer that this is the repository-level history listing.

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 guidance, no exclusions, and no mention of alternatives. The phrase 'optionally starting from a commit-ish' describes a parameter rather than a usage condition, so the agent gets no help choosing between this and pr_commits or repo_commit_get.

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