Skip to main content
Glama

slots

Read-only

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

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": "slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDirección de la página: forma completa o parte inicial con barra diagonal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/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 safety and closed-world scope are covered upstream. The description adds only that output is derived from a page address; it says nothing about what happens with an off-site or invalid URL, whether the page must belong to the same site, failure behavior, or the shape of the returned data — notable given the openWorldHint=false constraint on the URL.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no padding, and the verb is front-loaded. However, the sentence spends its length on an indirect circumlocution ("lo que una página muestra sobre su juego") instead of naming the extracted entity directly, so brevity comes at the cost of clarity.

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 carries the burden of explaining what comes back from the page, and it does not — the return value's structure is entirely unstated. For a single-param fetch tool whose openWorldHint=false implies URL scope restrictions, the definition should at minimum state the closed-site constraint and expected result content.

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% and the single url parameter is fully documented, including that it may be a full address or a leading portion with a trailing slash. The description restates that the URL drives the result but contributes no additional syntax, normalization, or format meaning beyond the schema — baseline 3 is appropriate.

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 resource ("lo que una página del sitio muestra sobre su juego o su listado de juegos"), so the general shape is discernible. But the phrasing is indirect and circular — it describes a page's content in terms of itself — and it never states plainly that this is a page-scraping/extraction tool for slot/game data, nor does it distinguish itself from siblings like buscar_maquinas or juegos_gratis.

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 guidance, no mention of prerequisites, and no routing to alternatives. The agent must infer from the name and the sibling list whether this is the right tool for a given lookup rather than a search tool.

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