Skip to main content
Glama

lookup_slots

Read-only

Name-based page finder for games, game studios and collections. Topics, themes and descriptions are not part of the match. Reviews published: 27

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": {
      "query": "<query>"
    },
    "name": "lookup_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTwo or more characters from the name of a game, a game studio or a collection.

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 a genuine behavioral constraint beyond annotations — the match is strictly on names, not topics/themes/descriptions — but says nothing about result ordering, limits, or how many pages may be returned.

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 two sentences are compact and front-loaded with the scope and its exclusion. The trailing fragment 'Reviews published: 27' does not belong to a usage instruction, has no clear meaning in context, and dilutes an otherwise tight definition.

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 single-parameter read-only lookup with full schema coverage and no output schema, the description supplies the essentials: what is searched, what is excluded. The only gap is that what a 'page' contains is never described, which is a minor omission given the tool's simplicity.

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 query parameter is fully documented with minimum and maximum lengths. The description's statement that the query covers game, studio and collection names is consistent with the schema but adds little beyond it, so 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?

The description names a specific action and resource set: a name-based page lookup across games, game studios and collections. That is concrete enough to distinguish it from unrelated siblings such as free_pokies and jackpots, though the term 'page finder' leaves the returned entity type slightly ambiguous.

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 usefully states a negative condition — topics, themes and descriptions are not matched — which tells the agent what kinds of queries will fail. It does not give positive when-to-use guidance, prerequisites, or point to any alternative tool for non-name searches, so the guidance is only implied.

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