Skip to main content
Glama

find_games

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. Review count: 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": "find_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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral constraint — the searchable fields are names only, not topics/themes/descriptions — but leaves unexplained what the trailing 'Review count: 20' refers to, and says nothing about match semantics (prefix, substring, fuzzy) or result limits.

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 front-loaded and earn their place, but the isolated fragment 'Review count: 20' is cryptic and lacks context, weakening 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 search tool with no output schema, the description covers what is searched, what is not, and the input expectation. The main gap is the ambiguous 'Review count: 20' note and unstated result/match behavior, which are minor 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?

Schema description coverage is 100%, so the single 'q' parameter is already fully documented, including its two-character minimum. The description adds only the domain hint that q should be a game, studio or collection title or fragment, which is largely redundant with the schema; 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 uses a specific verb ('Searches') and explicitly scopes the resource: the names of game pages, studio pages and collection pages. It also states a negative boundary — topics, themes and descriptions are not searched — which sharpens the purpose further. It doesn't differentiate against named siblings like best_jackpots, but the scope is clear enough on its own.

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 exclusion note ('Topics, themes and descriptions are not searched') implicitly tells an agent when this tool will fail, which is useful implied guidance. However, there is no explicit statement of when to prefer this over alternatives, and the sibling tools are not mentioned, so the agent must infer routing.

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