Skip to main content
Glama

Camino al Mil

Gol por número

gol_numero
Read-only

El gol número N de la carrera de Cristiano Ronaldo (1 = el primero), con fecha, rival, competición y fuentes.

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": {
      "numero": "<numero>"
    },
    "name": "gol_numero"
  }
}

Input Schema

NameRequiredDescriptionDefault
numeroYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a safe, closed read (readOnlyHint true, openWorldHint false). The description adds value by enumerating the returned fields (fecha, rival, competición, fuentes), which matters since there is no output schema, but it stays silent on what happens when N exceeds the total goal count.

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 tight sentence that front-loads the resource and parenthetically resolves the indexing ambiguity. No redundant wording, though it could afford one clause on out-of-range behavior without bloat.

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 one-parameter read tool with no output schema, the definition covers the resource, the parameter meaning, and the returned fields. It is still incomplete on edge cases: ordinal exceeding the career total, and whether goals are ordered by date or chronology across competitions.

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 0%, so the description must carry the parameter meaning, and it does clarify that 'numero' is a 1-based ordinal of career goals in order. It does not state any upper bound or out-of-range behavior, so the schema's minimum:1 is only partially complemented.

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 resource — the Nth career goal of Cristiano Ronaldo — and disambiguates the ordinal meaning with '(1 = el primero)'. It does not distinguish itself from siblings like buscar_goles or goles_en_fecha, which is the only gap.

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: look up one specific goal by its ordinal position. There is no explicit when-to-use versus when-not, and no pointer to alternatives such as buscar_goles for filtered queries or contar_goles for totals.

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