Skip to main content
Glama

find_reels

Read-only

Matches pages of games, game studios and collections by name only; the given text is not looked for in themes or descriptions. Review count: 21

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch text consisting of a full or partial game, studio or collection name, two characters at minimum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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. The description adds the meaningful behavioral detail that matching is restricted to names and not themes or descriptions, but the trailing "Review count: 21" is unexplained metadata that conveys no callable behavior.

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?

The first sentence is front-loaded and efficient, stating scope and the exclusion in one breath. The second fragment, "Review count: 21", does not earn its place and reads like stray metadata rather than tool guidance.

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 read-only search with a fully documented schema and no output schema, the description covers what is matched and what is excluded, which is close to sufficient. Only the unexplained review-count fragment and the lack of any result-shape hint keep it from being fully 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 description coverage is 100%, and the single parameter q already documents its min/max length and that it accepts a full or partial name. The description's name-only matching note reinforces the schema but adds no syntax or formatting detail beyond it.

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 states a specific verb ("Matches") and specific resources ("pages of games, game studios and collections"), plus a scope qualifier ("by name only"). An agent can tell what it searches, though nothing distinguishes it from the sibling tools new_jackpots and pokies.

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?

It gives a useful negative constraint: the query is not matched against themes or descriptions, so the agent knows name-only input is required. However, it offers no explicit when-to-use guidance or routing to an alternative tool for keyword/theme search.

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