Skip to main content
Glama
AI-SDLC Prompts MCP Server

AI-SDLC Prompts MCP Server

Siguiente prompt recomendado

recommend_next

Returns the prompt or prompts recommended by the editorial contract after a specified prompt, helping AI agents continue the SDLC sequence.

Instructions

Devuelve el/los prompt(s) que el contrato editorial recomienda usar después de uno dado.

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

Input Schema

NameRequiredDescriptionDefault
idYesId del prompt actual.
langNoIdioma de salida (es/en). Por defecto: es.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never states that this is a read-only lookup, what happens when no successor exists (empty list vs. error), or how many prompts may come back beyond the vague 'el/los'. The term 'contrato editorial' is also unexplained jargon an agent cannot act on.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity leaves gaps that a slightly longer sentence could have closed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description must explain the return value — but it only says 'el/los prompt(s)', leaving unclear whether the response contains ids, full prompt objects, or ordering. For a tool whose entire value is the returned successor set, that is a significant omission.

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%: both `id` ('Id del prompt actual') and `lang` (with es/en enum and default) are already documented. The description adds no format, default, or constraint detail beyond the schema, so the baseline 3 applies.

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 a specific resource ('el/los prompt(s) que el contrato editorial recomienda'), plus the relational scope ('después de uno dado'). This makes the chaining/recommendation purpose clear and separates it from sibling lookups like get_prompt, though it never names those siblings explicitly.

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?

The phrase 'después de uno dado' implies the workflow position — call it once you have a current prompt id — but there is no explicit when-to-use, no when-not, and no pointer to get_prompt/resolve_prompt as alternatives for non-recommendation retrieval. Guidance is implied rather than stated.

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