Skip to main content
Glama

Explorar relaciones de contenido

explorar_relaciones
Read-onlyIdempotent

Grafo con relaciones entre AppInitDev, apps y artículos enlazados por slug en ruta (relaciones heurísticas etiquetadas).

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

Input Schema

NameRequiredDescriptionDefault
limiteNoCantidad maxima de relaciones devueltas, entre 1 y 10 (predeterminado: 5).
paqueteNoPaquete Android opcional de la aplicacion cuyas relaciones se consultaran.
consultaNoNombre, slug o texto opcional para buscar relaciones entre apps y articulos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / consulta / description
      Added value: +"Nombre, slug o texto opcional para buscar relaciones entre apps y articulos."
    • addedInput schema / properties / limite / description
      Added value: +"Cantidad maxima de relaciones devueltas, entre 1 y 10 (predeterminado: 5)."
    • addedInput schema / properties / paquete / description
      Added value: +"Paquete Android opcional de la aplicacion cuyas relaciones se consultaran."
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the caveat that relations are 'heurísticas etiquetadas' and derived from slug matching in route. That is a genuinely useful reliability signal, but the description says nothing about the shape of returned nodes/edges or how many hops the graph spans, despite there being no output schema.

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 compact sentence with no filler, and the core concept is front-loaded. The compression comes at the cost of being a fragment rather than a statement of what the call does, but nothing is redundant.

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 output schema and three free-form parameters, the description would need to explain what a relation object contains and how consulta/paquete interact. It gives only the entity types and the heuristic caveat, leaving the agent to guess at result structure and usage, so it falls short for a discovery tool of this complexity.

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 all three optional parameters (limite, paquete, consulta) are already documented with bounds and defaults. The description does not reference any parameter or add semantics such as how consulta matches across apps versus articles; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (a graph of relations among AppInitDev, apps and articles) and the linking key (slug in route), which is more specific than the bare name. However, it is a noun-phrase fragment with no verb, so it never states the action of querying/exploring, and it does not differentiate itself from siblings like buscar_conocimiento or obtener_articulo that also surface related content.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says when this graph is preferable to buscar_apps, obtener_app or obtener_articulo, and no prerequisites or exclusions are given. The agent must infer usage entirely from the tool name.

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.