Skip to main content
Glama
AI-SDLC Prompts MCP Server

AI-SDLC Prompts MCP Server

Listar prompts

list_prompts

List AI-SDLC Pro prompts by section, risk, autonomy, or free text search, with Spanish/English output.

Instructions

Lista los prompts de la biblioteca AI-SDLC Pro, con filtro opcional por sección (00-17), riesgo esperado (low/medium/high/variable), autonomía permitida (A0-A3) y texto libre (busca en título y descripción).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoIdioma de salida (es/en). Por defecto: es.
riskNo
queryNoTexto libre a buscar en título/descripción.
sectionNoCódigo de sección, ej. '07', '16'.
autonomyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; 'Lista' does convey a non-mutating read, and it discloses that free-text search covers título and descripción. It does not describe the returned shape, ordering, or whether all prompts are returned when no filter is given, leaving meaningful behavioral gaps.

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?

A single dense sentence with the resource first and the optional filters following; every clause carries information and 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 five-parameter, all-optional listing tool with no output schema and no annotations, the description covers four of the five parameters with concrete value ranges and clarifies search semantics. Only 'lang' is unaddressed, and return-shape details are absent, but both are minor for this tool type.

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?

Beyond the 60% schema coverage, the description supplies value ranges the schema lacks: section codes 00-17, risk values low/medium/high/variable, and autonomy A0-A3, plus the semantics of the free-text search field. It omits the 'lang' parameter entirely, which the schema does describe but the description does not reinforce.

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?

The description uses a specific verb ('Lista') plus a concrete resource ('prompts de la biblioteca AI-SDLC Pro'), so an agent immediately knows what it returns. It does not explicitly name the sibling it differs from (get_prompt for a single item, resolve_prompt), so differentiation must be inferred from plural-form naming.

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?

It states that all filters are optional, implying a 'browse/list, then narrow down' usage pattern. However, it never says when to choose this over get_prompt or recommend_next, nor does it state exclusions or prerequisites.

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