Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Schema quality: 20 required parameters missing descriptions, 92 optional parameters undescribed

Abierto
#2,425 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@RossTarrant ya está trabajando en esto.

Desde el 1/6/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Running static schema analysis on the GitHub MCP server reveals 112 issues (20 errors, 92 warnings) across 26 tools. The most impactful: required parameters with no description, which forces AI agents to guess what values to provide.

Summary:

Severity Count Impact
Error (E103) 20 Required parameters with no description
Warning (W102) 72 Optional parameters with no description
Warning (W103) 20 Required string params with no enum/pattern/example

Examples of what agents see:

create_issue requires title and body with no description. An agent doesn't know:

  • Is body plain text or markdown?
  • What's the maximum length?
  • Should title include a prefix like [BUG]?

search_repositories requires query with no description. An agent doesn't know:

  • Is this GitHub search syntax (language:go stars:>100)?
  • Or plain text?
  • What qualifiers are available?

create_pull_request requires title, body, head, base with no descriptions. An agent must guess:

  • Is head a branch name or a ref like refs/heads/feature?
  • Is base required to be main or can it be any branch?

What good parameter descriptions look like:

{
  "name": "query",
  "type": "string",
  "description": "GitHub search query using search syntax (e.g. 'language:go stars:>100'). See https://docs.github.com/en/search-github/searching-on-github"
}

How this was found:

mcp-assert lint --server "npx -y @modelcontextprotocol/server-github"

Adding descriptions to required parameters would significantly reduce agent misuse of these tools.

Lenguaje dominante
Go
Estrellas
33.1k
Forks
5k
Merge medio
2 d 1 h
PR fusionados (30 d)
25

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/github-mcp-server

Todos los issues de github/github-mcp-server

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.