Skip to main content
Glama
Sign In
MCP DevOps Kit

MCP DevOps Kit

by Jmfrodero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

github_list_repos

List all repositories for a GitHub user or organization. Filter by type and control pagination.

Instructions

List repositories for a GitHub user or organization

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

Input Schema

NameRequiredDescriptionDefault
ownerYesThe GitHub username or organization name
typeNoFilter by repository type: all, owner, public, privateowner
per_pageNoNumber of results per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details such as pagination handling, authentication needs, rate limits, or response structure. The schema hints at pagination via `per_page`, but the description does not mention this.

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 sentence with no wasted words, concisely conveying the core purpose.

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?

Given the lack of output schema and annotations, the description is minimal. It does not explain the output format or pagination behavior, leaving gaps for the agent to infer. Adequate but could be more informative.

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 coverage is 100%, so the schema already describes each parameter. The description adds no additional meaning beyond what is in the schema; it merely restates that the tool lists repos for a user or org.

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?

The description clearly states the verb 'List' and the resource 'repositories for a GitHub user or organization', which is specific and distinguishes it from siblings like `github_get_repo_info` for a single repo.

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?

The description implies usage for listing repos for a user/org but does not explicitly state when to use this tool versus alternatives like `github_get_repo_info` or when not to use it.

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