Skip to main content
Glama
AI-SDLC Prompts MCP Server

AI-SDLC Prompts MCP Server

Obtener framework

get_framework

Returns the mandatory AI-SDLC operating principle to prepend to any prompt, in Spanish or English. Use it to ensure the required framework preamble precedes library prompts.

Instructions

Devuelve el preámbulo obligatorio del framework AI-SDLC (principio operativo que se antepone a cualquier prompt de la biblioteca).

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

Input Schema

NameRequiredDescriptionDefault
langNoIdioma de salida (es/en). Por defecto: es.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and "Devuelve" makes clear this is a content-returning read with no mutation. It also discloses behavior beyond the name: the returned text is a mandatory operating principle that must be placed ahead of any library prompt. It omits whether the content is static or versioned and says nothing about size or format, which keeps it below 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.

Conciseness5/5

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

One sentence, front-loaded with the return value and followed immediately by the qualifier that gives it meaning. No filler, no repetition of the title.

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 simple read tool with one optional parameter, no output schema, and no nested objects, the description covers what is returned and how it should be used. The main missing piece is any statement about determinism or versioning of the framework preamble, which matters if the text changes over time.

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?

The single optional lang parameter has a 100% described schema, including the enum values and the Spanish default, so the schema does the work. The description adds nothing about language behavior, and per the high-coverage baseline a 3 is appropriate.

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 and resource ("Devuelve el preámbulo obligatorio del framework AI-SDLC") and clarifies that this preamble precedes any library prompt, which implicitly separates it from get_prompt/list_prompts. It stops short of naming a sibling explicitly, so an agent must infer the boundary rather than read it.

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 "se antepone a cualquier prompt de la biblioteca" implies the tool should be called before fetching or using a prompt, which is useful implicit guidance. However, there is no explicit when-to-use statement, no when-not-to-use case, and no named alternative among get_prompt, list_prompts, recommend_next, or resolve_prompt.

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