Skip to main content
Glama
Sign In
GitHub MCP Server

GitHub MCP Server

by dantecaceres92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_repositories

Lists the authenticated user's GitHub repositories with names, descriptions, visibility, and URLs so you can answer repository questions or confirm a repo name before using other GitHub tools.

Instructions

Lista los repositorios del usuario autenticado en GitHub (nombre, descripción, visibilidad y URL). Úsalo cuando el usuario pregunte qué repositorios tiene, o para averiguar el nombre exacto de un repo antes de usar otro tool.

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_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoCriterio de orden: created, updated, pushed o full_name. Por defecto 'updated'updated
perPageNoCantidad de repositorios a listar (1-100). Por defecto 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the returned fields and implies authentication via 'usuario autenticado', but says nothing about pagination limits (only perPage is exposed, no page cursor), private vs public repo visibility, rate limits, or error behavior for unauthenticated calls.

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?

Two tight sentences: identity/scope first, then usage triggers. No redundant restatement of the tool name and no filler.

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 two optional params and no output schema, the description covers purpose, triggers and returned fields adequately. The one meaningful gap is that pagination beyond perPage is not addressed, which matters for users with many repositories.

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?

Both parameters are fully documented in the schema (100% coverage) including enum values, defaults and range, so the baseline is a 3. The description adds no ordering or pagination semantics beyond what the schema already states.

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?

States a specific verb and resource ('Lista los repositorios') plus the exact scope ('del usuario autenticado en GitHub') and even enumerates the returned fields (nombre, descripción, visibilidad, URL). An agent can distinguish this from list_commits or create_repository without opening any schema.

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

Usage Guidelines4/5

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

Gives explicit usage triggers: when the user asks what repositories they have, and as a lookup step to resolve an exact repo name before calling another tool. It lacks explicit exclusions or a named alternative, but the workflow context is clear and actionable.

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