Skip to main content
Glama

top_giros

Read-only

Devuelve, a partir de la dirección de una página de este sitio, la información que muestra sobre su juego o su listado de juegos.

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": {
      "url": "<url>"
    },
    "name": "top_giros"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDirección completa de la página, o la parte que empieza con una barra.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 elsewhere. The description adds that the input must be a page of 'este sitio' and that output concerns a game or a game listing, but it never describes the shape of the returned information, failure behavior for pages with neither, or any rate/access notes. Beyond the annotations, little context is added.

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 well-formed sentence, front-loaded with the action and the input source. It is not padded, though it is arguably under-specified rather than concise.

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

Completeness2/5

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

With no output schema, the description is the only place the return payload could be explained, and it says merely 'la información que muestra'. For a single-parameter scraper whose value depends entirely on what it extracts, that leaves a major gap for an agent deciding whether to call it.

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 100% — the single 'url' parameter is already documented as a full address or a path starting with a slash, with a 300-character cap. The description only restates that the input is a page address and adds no format, canonicalization, or relative-vs-absolute guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Devuelve') and a source ('a partir de la dirección de una página de este sitio') and scopes the result to 'su juego o su listado de juegos'. But 'la información que muestra' is vague — it never says what fields or content come back, so the agent cannot predict the output. It is recognizable as a site-scoped scraper/lookup but not sharply differentiated from the siblings.

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 versus alternatives guidance, no prerequisite about which URLs are valid, and no statement about when not to call it. The only implied usage is that you supply a page address from this site.

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