Skip to main content
Glama

Camino al Mil

Goles en un día del calendario

goles_en_fecha
Read-only

Qué goles marcó Cristiano Ronaldo en un día y mes cualquiera, sumando todos los años (la app «El gol de tu cumpleaños»). Si ese día no marcó, dice el día con gol más cercano.

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": {
      "mes": "<mes>",
      "dia": "<dia>"
    },
    "name": "goles_en_fecha"
  }
}

Input Schema

NameRequiredDescriptionDefault
diaYes
mesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuine context beyond them: results are summed across all years, and a miss does not return empty but instead reports the nearest day with a goal. That fallback behavior is the kind of detail an agent could not infer from the annotations.

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, no filler, with the core operation stated first and the fallback rule second. Every clause contributes information an agent needs.

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?

For a two-parameter read-only lookup with no output schema, the description covers what the tool returns (goals for that day) and how it behaves on a miss. The remaining gap is the shape of the response, such as whether goals are listed individually or as a count, which is minor for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it does: it makes clear that 'mes' and 'dia' are a calendar month/day with no year component and that the result aggregates every year. It does not discuss validation bounds, but those are already encoded in 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 gives a specific verb and resource: the goals Cristiano Ronaldo scored on any given day and month, aggregated across all years, framed by the 'El gol de tu cumpleaños' app. That is far more specific than the title alone and distinguishes it from counting or comparing siblings, though it never explicitly names an alternative tool.

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 birthday-app framing implies the intended use case (a calendar-day lookup) and the second sentence describes fallback behavior when the day has no goal. There is no explicit statement of when to prefer this over buscar_goles or contar_goles, so the guidance remains implicit.

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