Skip to main content
Glama

Camino al Mil

Buscar goles

buscar_goles
Read-only

Lista goles de Cristiano Ronaldo con filtros (rival, equipo, competición, año, fechas, jugada), en orden cronológico. Cada gol trae fecha, rival, competición, resultado y fuentes.

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_goles"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoNoAño natural del gol.
desdeNoFecha mínima, AAAA-MM-DD.
hastaNoFecha máxima, AAAA-MM-DD.
ordenNoantiguos
rivalNoRival, o parte del nombre. Sin distinguir tildes ni mayúsculas. Ej.: "Atlético".
equipoNoEquipo con el que marcó.
jugadaNoTipo de jugada, cuando la base lo tiene.
limiteNo
competicionNoCompetición, o parte del nombre. Ej.: "Champions" o "Mundial 2018".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a read-only, closed-world operation, so the safety profile is covered. The description adds value beyond that by disclosing ordering semantics and the fields each record carries (fecha, rival, competición, resultado, fuentes), which matters because there is no output schema. It stops short of describing pagination or result-volume behavior.

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 sentences, zero filler: the first front-loads scope, filters and ordering; the second covers return contents. Nothing is redundant or buried.

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?

With nine optional parameters, no output schema and no required fields, the definition covers the essentials: what is listed, how it is filtered, how it is ordered, and what each result contains. The remaining gap is behavior at scale (default limit of 20, max 100, truncation), which the schema implies but the description never mentions.

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 coverage is 78%, so the schema documents most parameters with its own descriptions and examples. The description only restates the filter dimensions already present in the schema and says nothing about "orden" or "limite", adding essentially no meaning beyond the structured fields.

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 ("Lista") and a precisely scoped resource ("goles de Cristiano Ronaldo"), and enumerates the filter dimensions plus the chronological ordering. This is enough to distinguish it from counting or date-lookup siblings, though no sibling is named explicitly.

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 description implies usage (filtered listing of goals) and notes the chronological order, which hints at when it applies. It never says when not to use it, nor points to contar_goles for aggregates or goles_en_fecha for single-date lookups, so routing must be inferred from the purpose line alone.

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