Skip to main content
Glama

search

Read-only

Name-based page finder for games, game studios and collections. Topics, themes and descriptions are not part of the match. Slot reviews: 20

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

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

B3.3/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 real behavioral context by restricting matching to names, but it says nothing about result ordering, result count, pagination, or why 'Slot reviews: 20' appears — leaving the agent unable to predict the response.

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 scope statement and the exclusion clause are front-loaded and earn their place, but 'Slot reviews: 20' is an unexplained fragment that reads as leftover metadata and forces the agent to guess. Two of three sentences are efficient; the third introduces noise.

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 this is close to adequate: the agent knows what is matched and what is not. It stops short of describing what a result page contains or what the '20' refers to, so the definition is not fully self-sufficient even for a tool this simple.

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?

With a single parameter at 100% schema coverage, the schema already defines q as a full or partial name of at least two characters. The description reinforces the semantics by stating that topics, themes and descriptions are not matched, which adds genuine meaning about what q will not retrieve. Baseline 3 is appropriate since the schema carries the syntax burden.

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+resource: a name-based page finder scoped to games, game studios and collections, and it explicitly bounds the match surface (names only). That distinguishes it in kind from list-style siblings like free_pokies and top_jackpots, though no sibling is named directly.

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 line 'Topics, themes and descriptions are not part of the match' implicitly tells the agent when this tool will fail (topical/thematic queries), which is useful negative guidance. However, no alternative tool is named for those cases, and the trailing 'Slot reviews: 20' is unexplained — it is unclear whether it is a result cap, a content count, or a hint to use another path.

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