Skip to main content
Glama

Mindep Slots UK

lookup_games

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

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

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is low, and the description usefully discloses the matching restriction on the query text. It does not explain what a result page contains or how pagination behaves despite saying 'pages of games'. The trailing 'Review count: 30' is unexplained metadata that adds ambiguity rather than behavioral clarity.

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 core sentence is front-loaded and efficient, and the exclusion is placed immediately after the positive scope. The appended 'Review count: 30' is orphaned noise with no stated meaning, which drags down an otherwise tight definition.

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?

For a one-parameter read-only lookup with full schema coverage and no output schema, the definition covers enough to invoke it correctly. Given the 'pages' wording, though, an agent has no information about result volume or paging behavior, and the dangling review-count figure is left unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline sits at 3 for the single 'q' parameter. The description earns one step above that by stating a negative constraint the schema does not: the supplied text is matched against names only, never themes or descriptions, which materially shapes how an agent should phrase the query.

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 definition gives a specific verb and resource set: it matches 'pages of games, game studios and collections' and constrains matching to names. That is considerably more precise than a tautological restatement. It stops short of 5 because it never distinguishes itself from the listed siblings (free_games, reels); the 'name only' clause scopes the search fields rather than the tool choice.

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 'by name only ... not looked for in themes or descriptions' clause implies the right context: call this when you have a title or fragment, not a topical query. However, no alternative is named for the excluded case, so an agent that wants thematic search is told what will not work without being routed anywhere.

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