Skip to main content
Glama
Sign In
GitHub MCP Server — AutomateHub

GitHub MCP Server — AutomateHub

by gnvidia06-ux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear repositorio

create_repository

Create a new personal GitHub repository, choose public or private visibility, and initialize it with a README to begin committing immediately.

Instructions

Crea un repositorio NUEVO en la cuenta personal de GitHub del usuario autenticado. Usala cuando el usuario pida crear, iniciar o armar un repo o proyecto nuevo. Por defecto es público y se crea con un README inicial. No la uses para ver repos existentes (para eso está list_repositories).

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

Input Schema

NameRequiredDescriptionDefault
nameYesNombre del repositorio, sin el owner. Ejemplo: 'mi-proyecto'.
privateNotrue para crear el repositorio como privado. Por defecto es público.
autoInitNoSi es true, crea el repo con un README inicial. Recomendado: permite hacer commits inmediatamente.
descriptionNoDescripción corta del repositorio.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: it is a write operation on the personal account, and defaults are public with an initial README. However it says nothing about failure modes (e.g., a name that already exists), required token scopes/permissions, or irreversibility, which matter for a create operation.

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?

Three short sentences, front-loaded with the core action, then the trigger conditions, then the default behavior, then the exclusion. No filler or redundant restatement of the title.

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 4-parameter creation tool with full schema coverage and no output schema, the description covers purpose, triggers, defaults, and the sibling alternative. The remaining gap is error/edge-case behavior on a mutation tool with zero annotation coverage, which keeps it from a 5.

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 description coverage is 100%, so all four parameters are already documented in the schema, setting the baseline at 3. The description restates the two defaults (public, README init) but adds no constraint or format detail beyond what the schema already provides.

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 ("Crea un repositorio NUEVO") and scopes it to the authenticated user's personal GitHub account. It also explicitly distinguishes itself from the sibling list_repositories, so an agent can separate creation from listing without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit positive triggers ("cuando el usuario pida crear, iniciar o armar un repo o proyecto nuevo") and an explicit exclusion with the alternative named ("No la uses para ver repos existentes (para eso está list_repositories)"). Both when-to-use and when-not-to-use are covered.

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