Skip to main content
Glama
Sign In
github-repo-mcp-server

github-repo-mcp-server

by technomad641
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_repos

Retrieve every GitHub repository in the server's allowlist along with its basic metadata to see what is available.

Instructions

List every repo in this server's allowlist, with basic metadata for each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses scope ('every repo') and content ('basic metadata') but does not mention pagination, output format, or authentication requirements. For a read-only list operation, this is adequate but not rich.

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 sentence that immediately states the action and scope. No unnecessary words or repetition, making it highly efficient and well-structured.

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?

Given the tool's simplicity (0 params, no output schema), the description is fairly complete. It specifies the purpose and scope, and 'basic metadata' sets expectations. However, it could be more explicit about what metadata fields are included or the exact return shape.

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?

The input schema has zero parameters, so the baseline is 4. The description adds no parameter info (none needed), but 'basic metadata' gives an indication of the output content, which is slightly beyond the schema.

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', the resource 'repo', and the scope 'every repo in this server's allowlist'. It distinguishes from siblings like get_repo (single repo) by emphasizing 'every repo' and 'allowlist'.

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 usage context is implied (when you need an overview of all approved repos) but no explicit alternatives are mentioned. It doesn't say when not to use this tool (e.g., when needing details for a specific repo, use get_repo).

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