Skip to main content
Glama

Mindep Slots UK

reels

Read-only

Given the address of a page, returns what the page shows: the details of one game or its list of games.

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

Input Schema

NameRequiredDescriptionDefault
urlYesIdentifies a page on this site by its complete address or by the part that begins with a slash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 the safety profile is covered and the bar is lower. The description adds the meaningful behavioral fact that the response shape varies (single game vs. list), but says nothing about invalid URLs, empty pages, or error behavior.

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?

One front-loaded sentence with no filler. The clause "returns what the page shows" is slightly redundant with the colon-delimited specification that follows, but the total size is well matched to a one-parameter tool.

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?

With one parameter, no output schema, and no nesting, the definition covers the essentials but leaves the return contract thin: no field names, no indication of how a game detail differs from a list, and no error semantics. Adequate, not complete.

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 in the schema, so the description's "address of a page" adds no meaning beyond it. Baseline 3 is appropriate when the schema does the work.

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?

"Given the address of a page, returns what the page shows" states a read operation over a URL and narrows the payload to game details or a game list. However, the framing is generic ("returns what the page shows") and the tool name "reels" does nothing to clarify it, so an agent cannot easily distinguish it from free_games or lookup_games.

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 exclusion of cases, and no mention of the sibling tools free_games and lookup_games. The agent must infer from the return shapes alone whether this or a sibling is the right call.

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