Skip to main content
Glama

Camino al Mil

Comparar con los máximos goleadores

comparar_goleadores
Read-only

Tabla de los máximos goleadores de la historia del fútbol (goles oficiales, con desglose por liga, copa, continental y selección) y el lugar de Cristiano Ronaldo. Opcional: filtrar por nombre.

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

Input Schema

NameRequiredDescriptionDefault
limiteNo
jugadorNoNombre o parte del nombre. Ej.: "Messi".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 useful context that goals are official and broken down by competition type, but says nothing about ordering, truncation by the limite default of 15, or what happens when the name filter matches nobody.

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 dense sentence plus a short optional-filter note. The core resource and scope come first, and no wording is wasted, though the competition breakdown parenthetical is somewhat packed.

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

Completeness5/5

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

For a two-parameter read-only lookup with no output schema and annotations covering safety, the description covers what data is returned and how filtering changes it. An agent has enough to call it correctly.

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 50%: jugador is documented with an example, while limite only carries default/min/max constraints. The description does not explain that limite caps the table size or what order rows appear in, so it adds little meaning beyond the schema.

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 specific resource (historical top scorers table with breakdown by league, cup, continental and national team) plus the added dimension of Cristiano Ronaldo's placement. It is clearly distinguishable from siblings like buscar_goles or contar_goles, though it never explicitly contrasts itself against them.

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 only says the player filter is optional ("Opcional: filtrar por nombre"), which implies when to supply it but gives no guidance on when to pick this tool over the sibling search/count tools. Usage is inferable but not framed as guidance.

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