Skip to main content
Glama

Search games

search_games
Read-onlyIdempotent

Find video games by name, on every platform or one. Each match comes with its platform, its page URL and what loose, complete and sealed copies typically sell for.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage of results, 24 a page, up to page 3.
queryYesThe game's name or words from it, e.g. "ocarina of time".
currencyNoCurrency for prices, an ISO 4217 code: USD (the default), EUR, GBP, CAD, AUD, JPY, PLN and others.
platformNoA platform slug from list_platforms, e.g. "playstation-2" or "nintendo-switch".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Page of results, 24 a page."New value: +"Page of results, 24 a page, up to page 3."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description then adds value annotations don't carry: each match includes platform, page URL, and typical loose/complete/sealed prices, which tells the agent what to expect without an output schema.

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?

Two tight sentences with the core action front-loaded and the return payload summarized second. No filler; the only mild redundancy is restating the platform choice already present in the title-and-schema framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With full schema coverage, four simple non-nested parameters, and read-only annotations, little is left to explain. The description closes the remaining gap by describing the return contents in the absence of an output schema.

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 page, query, currency and platform are already documented in the schema, making 3 the baseline. The description adds only the platform-optionality nuance ("every platform or one") and says nothing about currency or paging beyond what the schema states.

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?

States a specific verb and resource ("Find video games by name") plus the scope choice of all platforms versus one, and lists what a match returns. It is clear what the tool does, but it never names the sibling it differs from (e.g. get_game_prices), so the agent must infer the boundary.

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?

Usage is only implied: search by name, optionally narrowed to a platform. There is no explicit when-to-use or when-not-to-use guidance against get_game_prices or browse_platform. The one concrete pointer is that the platform value must come from list_platforms, which is genuinely helpful.

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