Skip to main content
Glama

Camino al Mil

Contador hacia los 1000 goles

contador
Read-only

Goles oficiales de Cristiano Ronaldo en su carrera, cuántos faltan para los 1000, fecha de corte, ritmo reciente, proyección 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": "contador"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and scope are covered. The description adds useful data-freshness and provenance context by disclosing a cutoff date, cited sources, and a projection component (i.e. part of the output is an estimate, not a hard count). It does not say how current the snapshot is or how the projection is derived.

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 sentence with a compact comma list, front-loaded with the core subject and the headline metric (goals remaining to 1000). Every item in the list corresponds to something the tool actually reports, so nothing is filler.

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?

With no parameters, no nested objects and no output schema, the description carries the full burden of explaining what comes back, and it does so by listing every return component. Combined with the read-only annotations, an agent has enough to invoke it correctly and set expectations about freshness and estimates.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The enumerated output components are the only semantic content needed at call time.

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 the exact resource (Cristiano Ronaldo's official career goals) and enumerates the specific outputs: total, remaining to 1000, cutoff date, recent pace, projection and sources. An agent can tell this is a progress-summary tool rather than a raw search. It stops short of distinguishing itself from siblings such as contar_goles or gol_numero, which plausibly overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no exclusions, and no reference to alternatives. The content list only implies the use case ('how many goals, how close to 1000'), leaving the agent to guess whether to call this or a counting/search sibling.

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