Skip to main content
Glama
AI-SDLC Prompts MCP Server

AI-SDLC Prompts MCP Server

Obtener prompt

get_prompt

Fetches a software development lifecycle prompt by ID, returning its title, description, raw template with placeholders, usage formulas, editorial contract, and recommended next prompts.

Instructions

Devuelve el detalle completo de un prompt por id: título, descripción, texto crudo del prompt (con placeholders [ASI] sin resolver), fórmulas de uso, contrato editorial y siguiente(s) prompt(s) recomendado(s).

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

Input Schema

NameRequiredDescriptionDefault
idYesId del prompt, ej. '07-06-pruebas-performance-carga'.
langNoIdioma de salida (es/en). Por defecto: es.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and it does well: it discloses exactly what comes back, including the important caveat that placeholders remain unresolved and that editorial contract and next-prompt recommendations are bundled in. It does not mention error behavior for an unknown id or any auth/rate considerations, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence with the resource and id lookup front-loaded, followed by the field list. No filler, though the enumeration of returned fields is long enough to be slightly heavy for a single sentence.

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?

With no output schema and no annotations, the description must describe the return payload, and it does so thoroughly, including the unresolved-placeholder behavior that would otherwise surprise an agent. Only the lang parameter and failure modes are left uncovered.

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 coverage is 100% and both parameters (id, lang) are documented with an example id and an enum, so the schema does the heavy lifting. The description adds only 'por id' and never mentions the lang parameter, so it adds little beyond structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Devuelve') and resource ('detalle completo de un prompt por id') and enumerates the returned fields (título, descripción, texto crudo, fórmulas, contrato editorial, siguientes prompts). The parenthetical that [ASI] placeholders come back 'sin resolver' implicitly separates it from resolve_prompt, though no sibling is named outright.

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?

Retrieval by id is clearly implied, but there is no explicit statement of when to use this versus resolve_prompt (which presumably resolves the placeholders) or list_prompts. The agent must infer the routing from the 'sin resolver' hint alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.