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

[W9.5] Align the MCP tool, resource, and prompt catalogs with the current CLI

Cerrado
  • ¿Algo no está bien?
#171 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ruby
Área
cli, devtools, testing

Línea de trabajo

Start by comparing the exposed MCP tools and argument schemas with the current CLI, then trace schema-driven execution and the existing MCP discovery and behavior tests. Map supported tools, arguments, defaults, and CLI equivalents; identify unsupported commands and options. Done means supported workflows, prompts, and resources are aligned, pinning and offline behavior are verified, and each change has passing tests in its own PR.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: cli enhancement

Context

The MCP catalog exposes a subset of OPSd commands and options. The current CLI also supports explicit module synchronization, platform rendering, and offline platform validation, so supported MCP workflows must be selected and described deliberately.

Scope

  • Compare all exposed tools and argument schemas with current CLI behavior.

  • Implement support for explicit modules sync, platform rendering, and offline validation where needed for the supported setup-to-render workflow.

  • Record intentionally unsupported CLI commands and options instead of implying full parity.

  • Update schemas, descriptions, reusable prompts, and resource pointers together.

  • Keep module synchronization explicit; render must not silently update dependency pins.

  • Extend schema and SDK-driven behavior tests in the same PR as each catalog/argument change. Verify discovery schemas and that exposed options reach actual execution, including module pin preservation and the documented offline behavior. Run these tests in the existing MCP CI suite.

Acceptance criteria

  • A documented mapping lists supported MCP tools, arguments, types, defaults, and relevant CLI equivalents.

  • The supported infrastructure and platform workflows have all prerequisites available through MCP or explicit documented setup steps.

  • Exposed options reach the execution layer and are covered by meaningful behavior tests.

  • Prompts and resources refer to existing commands, paths, and supported capabilities.

  • Offline behavior and module synchronization preserve the CLI pinning contract.

  • Each catalog/workflow change is delivered with passing discovery/schema and execution tests in its own PR; supported behavior is not left untested until W9.6.

Related

Parent: #166. Coordinate with #168 and #170.

Lenguaje dominante
Ruby
Estrellas
0
Forks
0
Merge medio
11 h 37 min
PR fusionados (30 d)
35

Preparar el entorno

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 opsd-io/opsd-cli

Todos los issues de opsd-io/opsd-cli

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.