Skip to main content
Glama

lookup_slots

Read-only

Searches the names of game pages, game studio pages and collection pages for the entered text. Topics, themes and descriptions are not searched. Reviews: 10

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_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFull or partial name of a game, game studio or collection, at least two characters long.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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, matching a safe lookup over a closed catalog, and the description is consistent with that. The name-only matching boundary is useful added behavior, but the trailing fragment 'Reviews: 10' is unexplained and adds no actionable meaning.

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?

The core scope and the exclusion are front-loaded in two tight sentences with no filler. The trailing 'Reviews: 10' is stray, unexplained text that does not earn its place.

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 search over a known catalog, the definition covers what is searched and what is not. It says nothing about result shape, result caps or ordering, which matters since no output schema exists, and the 'Reviews: 10' fragment is left ambiguous.

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% and the single param is documented as a full or partial name, so the baseline is 3. The description adds value by clarifying that the match is applied only against page names and never against topics, themes or descriptions, which tells the agent how to phrase q.

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 names a specific verb ('Searches') and a precise resource scope: names of game pages, studio pages and collection pages. An agent immediately knows what corpus is being matched, though nothing in the text distinguishes it from siblings online_slots or pokies, whose names alone convey no behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit exclusion boundary: topics, themes and descriptions are NOT searched, which tells the agent when this tool will fail to find something. It stops short of naming an alternative tool for full-text/description lookups, so guidance is clear but not complete.

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