Skip to main content
Glama
AI-SDLC Prompts MCP Server

AI-SDLC Prompts MCP Server

Resolver prompt con variables

resolve_prompt

Resolves prompt placeholders with provided variables, optionally includes the framework preamble, and returns the resolved text plus any required or optional placeholders left unresolved.

Instructions

Sustituye los placeholders del prompt (y opcionalmente del preámbulo del framework) con las variables provistas -- misma sustitución que hace el sitio. Las claves de 'variables' son los campos canónicos (repositorio, referencia, rama_actual, rama_destino, ambiente, componentes, modulo, stack, tipo_proyecto, metodologia, agentes, autonomia, entrada, objetivo, responsable, workspace, compliance, documentos, profundidad, adicionales), no los alias en mayúsculas del texto. Devuelve el texto resuelto y los placeholders obligatorios/opcionales que quedaron sin resolver.

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": "resolve_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId del prompt a resolver.
langNoIdioma de salida (es/en). Por defecto: es.
variablesNoCampo canónico -> valor.
append_contractNoAnexa el contrato de operación del prompt -- techo de autonomía, herramientas permitidas, criterios de detención y evidencia mínima (default: true). Desactivarlo entrega el prompt sin sus límites.
prepend_frameworkNoAntepone el preámbulo obligatorio del framework (default: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description does real work: it equates the substitution with the site's behavior, discloses that unresolved mandatory/optional placeholders are returned alongside the resolved text, and warns that keys must be canonical. It stops short of stating read-only semantics or what happens on an invalid id.

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?

Three sentences, front-loaded with the core action, then the key-naming caveat, then the return value. The long canonical-key list is dense but earns its place; nothing is redundant.

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 5-parameter tool with a nested object and no output schema, the description covers the return shape, the variable key contract, and the effect of the preamble flag. Minor gaps remain around the meaning of 'id' and failure behavior for unknown prompts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning by enumerating the canonical variable keys (repositorio, rama_actual, ...) and explicitly ruling out the uppercase aliases that appear in the prompt text. That is information the schema's "Campo canónico -> valor" note does not supply.

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?

Opens with a specific verb+resource ("Sustituye los placeholders del prompt") and scopes it precisely, including the optional framework preamble. It also states the return payload, so an agent can distinguish this resolution step from the raw-fetch siblings (get_prompt, get_framework) without opening a schema.

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?

Usage is implied rather than stated: the mention of variable substitution and the optional preamble suggests you call this when you have concrete variable values, but it never says when to prefer it over get_prompt or what to do if you lack values. No explicit exclusions or prerequisites are given.

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