Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

list_commits

Retrieve recent commits from a GitHub repository by specifying the owner and repository name to track code changes and development history.

Instructions

List recent commits for a repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes

Implementation Reference

  • The handler function for the 'list_commits' tool. It validates the owner and repo arguments, checks for GitHub token configuration, and calls the GitHubClient's listCommits method.
    async list_commits(args: Record<string, unknown>) {
      if (!cfg.githubToken) throw new Error("GITHUB_TOKEN is not configured");
      const owner = String(args.owner || "");
      const repo = String(args.repo || "");
      if (!owner || !repo) throw new Error("owner and repo are required");
      return client.listCommits(owner, repo);
    },
  • The input schema defining the required 'owner' and 'repo' string parameters for the list_commits tool.
    inputSchema: {
      type: "object",
      properties: {
        owner: { type: "string" },
        repo: { type: "string" },
      },
      required: ["owner", "repo"],
    },
  • The tool registration object that defines the name, description, and input schema for 'list_commits' within the registerGitHub function.
    {
      name: "list_commits",
      description: "List recent commits for a repository",
      inputSchema: {
        type: "object",
        properties: {
          owner: { type: "string" },
          repo: { type: "string" },
        },
        required: ["owner", "repo"],
      },
    },
  • The GitHubClient helper method that makes the API request to list commits for the given repository.
    listCommits(owner: string, repo: string) {
      return this.request(`/repos/${owner}/${repo}/commits`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('list') but doesn't reveal critical traits such as whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior, or what the output format looks like. For a tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence with zero wasted words. It front-loads the core purpose ('List recent commits for a repository'), making it immediately clear. Every part of the sentence earns its place by specifying the action and target resource.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 required parameters), lack of annotations, and no output schema, the description is incomplete. It fails to address key aspects like authentication needs, result limitations (e.g., what 'recent' entails), or error handling. For a tool with this context, more detail is necessary to ensure reliable use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'repository' but doesn't explain the 'owner' and 'repo' parameters beyond what's implied. No details are provided on parameter formats (e.g., GitHub username vs. organization for 'owner'), making it inadequate for guiding proper invocation.

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 'List recent commits for a repository' clearly states the verb ('list') and resource ('commits for a repository'), making the tool's purpose immediately understandable. It distinguishes from siblings like 'search_repositories' or 'get_repository_info' by focusing specifically on commits. However, it lacks specificity about what 'recent' means (e.g., time frame or count), preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'search_repositories' or 'get_repository_info', nor does it specify prerequisites (e.g., needing repository access) or exclusions. The agent must infer usage from the purpose alone, which is insufficient for effective tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/muti-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server