Skip to main content
Glama

buscar_alternativas

Read-only

Busca alternativas europeas a una herramienta o por texto libre. Úsala cuando alguien quiera dejar un software de fuera de Europa. Ejemplo: herramienta="slack".

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": {
      "limite": "<limite>"
    },
    "name": "buscar_alternativas"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoTexto libre, por ejemplo "facturación".
paisNoPaís de la empresa, ISO alfa-2.
limiteYesCuántos resultados devolver (1-20).
herramientaNoClave de la herramienta que se quiere sustituir, en minúsculas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a worked example ('herramienta="slack"') that clarifies input format, but says nothing about result ordering, whether non-European matches are ever returned, or how q and herramienta interact.

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?

Two front-loaded sentences plus a short example; the purpose comes first, followed by the trigger condition, with no filler wording.

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

Completeness3/5

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

For a four-parameter read-only search tool with full schema coverage the definition is serviceable, but it leaves the main behavioral ambiguity unresolved: whether q and herramienta are alternatives or combinable, and what the caller gets back.

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%, so each of the four parameters is already documented, including the ISO alpha-2 format and the 1-20 limit. The description adds only a format example for herramienta and does not resolve precedence between q and herramienta when both are supplied.

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 ('Busca alternativas europeas') and distinguishes two search modes: by tool key or by free text. It is clearly separable from siblings like listar_categoria or obtener_producto, though it never names an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Úsala cuando alguien quiera dejar un software de fuera de Europa' gives a concrete when-to-use condition tied to the user's intent. There is no explicit when-not guidance and no mention of when to prefer listar_categoria or comprobar_cumplimiento instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources