Skip to main content
Glama

Camino al Mil

Contar goles por grupo

contar_goles
Read-only

Cuenta goles de Cristiano Ronaldo agrupados por equipo, rival, competición, torneo, año o jugada. Admite los mismos filtros que buscar_goles; por ejemplo, rivales más goleados en la Champions.

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": {
      "agrupar_por": "<agrupar_por>"
    },
    "name": "contar_goles"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoNoAño natural del gol.
desdeNoFecha mínima, AAAA-MM-DD.
hastaNoFecha máxima, AAAA-MM-DD.
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
agrupar_porYes
competicionNoCompetición, o parte del nombre. Ej.: "Champions" o "Mundial 2018".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 safety is covered. The description adds the filter-reuse behavior with buscar_goles, but omits what the response looks like (group key plus count), how groups are ordered, and critically that 'limite' caps the number of returned groups rather than goals. For an aggregation tool with no output schema this is a meaningful gap.

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 compact sentences with the core action front-loaded and the example used efficiently to show a real query shape. No filler, though the sentence could have spent a few of those words on the limit/output behavior instead.

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?

The description covers the nine-parameter surface well through the 'mismos filtros que buscar_goles' clause and the dimension list, so an agent can form a correct call. The remaining gap is result semantics — ordering and the meaning of limite — but with read-only annotations present and a simple aggregate operation, the omission is not disqualifying (revised to 4 given the filter coverage).

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?

With 78% schema description coverage the schema already documents ano, desde, hasta, rival, equipo, jugada and competicion. The description adds no syntax or behavioral detail beyond that, and leaves the undocumented 'limite' parameter (default 25, max 300) completely unexplained, even though its meaning — truncating group results — is the one thing an agent most needs to know.

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 ('Cuenta goles de Cristiano Ronaldo agrupados por...') and enumerates the aggregation dimensions, so the agent knows this is an aggregate/count tool rather than a listing. It distinguishes itself from buscar_goles by noting it shares filters but aggregates, though it does not differentiate itself from the sibling 'contador', which by name may also count.

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?

Usage is implied rather than stated: aggregation by a dimension, plus a concrete example ('rivales más goleados en la Champions'). There is no explicit 'use this instead of X when...' rule and no mention of when not to use it, so the agent must infer that buscar_goles returns rows while this returns grouped counts.

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