Skip to main content
Glama

Best Online Slots UK

search_reels

Read-only

Name-based page finder for games, game studios and collections. Topics, themes and descriptions are not part of the match. Review count: 30

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": {
      "q": "<q>"
    },
    "name": "search_reels"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesA game, studio or collection title, or a fragment of one, containing two or more characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the substantive behavioral rule that matching is name-only and excludes topics, themes, and descriptions. That is real context an agent could not get from annotations. The trailing "Review count: 30" is unexplained — it is unclear whether it describes a returned field, a result limit, or a quality metric, which weakens the disclosure.

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?

Two tight sentences front-load the scope and then the exclusion, which is good ordering. The dangling "Review count: 30" fragment is unclear and does not obviously earn its place, slightly hurting structure.

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

Completeness4/5

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

For a one-parameter lookup tool with full schema coverage and annotations covering safety, the description supplies what is needed to call it correctly: what is matched and what is not. The only gap is the ambiguous "Review count: 30" note, which adds uncertainty rather than completeness.

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 100% and the single parameter already documents title-or-fragment matching with a 2–64 character range. The description's mention of "name-based" and fragment matching echoes the schema rather than extending it, so the baseline 3 applies.

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?

"Name-based page finder for games, game studios and collections" gives a specific verb and an explicit resource scope (pages, not raw entities). The negative clause "Topics, themes and descriptions are not part of the match" further sharpens what the tool actually does. It does not reference siblings, but the listed siblings are unrelated domains, so differentiation is not needed here.

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?

The exclusion of topic/theme/description matching implies the right usage (use this only when you have a title or title fragment), which is useful implied guidance. However, no explicit when-to-use sentence or alternative is named for the case where the caller has a topic or description instead — the agent must infer that this tool is wrong for that job.

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