Skip to main content
Glama

Camino al Mil

Explorar la vitrina de trofeos

buscar_trofeos
Read-only

Inventario documentado de títulos, premios, formación, amistosos, goleadores, equipos ideales, reconocimientos y podios de Cristiano Ronaldo. Devuelve ediciones, equipos, notas, fuentes y criterio de inclusió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": "buscar_trofeos"
  }
}

Input Schema

NameRequiredDescriptionDefault
equipoNo
nombreNoNombre o parte del nombre del trofeo, sin distinguir tildes.
categoriaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / equipo / description
      Removed value: -"Equipo con el que marcó."
    • changedInput schema / properties / equipo / enum
      Previous value: -[
      -  "sporting-cp",
      -  "manchester-united",
      -  "real-madrid",
      -  "juventus",
      -  "al-nassr",
      -  "portugal"
      -]New value: +[
      +  "sporting-cp",
      +  "manchester-united",
      +  "real-madrid",
      +  "juventus",
      +  "al-nassr",
      +  "portugal",
      +  "nacional",
      +  "portugal-sub20",
      +  "andorinha",
      +  "carrera"
      +]
  2. Added

TDQS

B3.2/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 does add value by disclosing what the payload contains (editions, teams, notes, sources, inclusion criteria), which compensates for the absent output schema, but says nothing about result size, ordering, or what an empty match returns.

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?

Two tight sentences with no filler: scope first, then return content. The long enumeration of trophy categories is dense but each item is informative rather than redundant.

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 three-optional-parameter read-only lookup with no output schema, the description covers scope and return fields adequately. It stops short of explaining how the filters interact or what the 'criterio de inclusión' actually means in practice, which an agent might need before trusting completeness of results.

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 low (33%) — only 'nombre' is annotated — but two of the three parameters are closed enums whose allowed values (e.g. sporting-cp, real-madrid, individual/club/seleccion) are largely self-explanatory. The description adds no meaning about filtering behaviour or whether the 'carrera' value in 'equipo' means an aggregate view, so it does not compensate for the gap.

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 names a concrete resource — a documented inventory of Cristiano Ronaldo's titles, awards, training, friendlies, top scorer honours, ideal teams, recognitions and podiums — which is clearly distinct from the goal-scoring siblings like buscar_goles or contar_goles. The retrieval verb is only implied by 'Inventario' / 'Devuelve', but the subject matter is unambiguous.

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 statement of when to use this tool versus alternatives, nor any exclusion guidance; the agent must infer from the topic that this is the non-goal, trophy/awards catalogue. Nothing tells the caller whether filters are combinable or when to omit them.

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