Skip to main content
Glama

search_games

Search the Infinite Backlog game catalog by title to get each match's name, slug, year, and category; use the slug with other tools to manage the game.

Instructions

Search the Infinite Backlog catalog. Returns name, slug, year and category per hit.

Use the slug with the other tools. Duplicate titles get IGDB-style slugs (Hades 1995 is hades, Hades 2020 is hades--1).

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
limitNo
queryYes
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 10,
      +  "title": "Limit",
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
    • removedInput schema / properties / wait_ms
      Removed value: -{
      -  "default": 2500,
      -  "title": "Wait Ms",
      -  "type": "integer"
      -}
  2. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must disclose behavior itself. It does add a genuine trait by explaining the duplicate-title slug scheme (hades vs hades--1), but it says nothing about match semantics (exact vs fuzzy vs substring), pagination, or the fact that this is a side-effect-free read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short lines, front-loaded with purpose and return shape, then workflow and the one non-obvious edge case. Nothing is wasted and nothing important is buried.

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?

An output schema exists and the return fields are already named, so not restating them is fine. The remaining gap is input-side: with 0% schema coverage, the meaning and effect of query/limit/offset should have been described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, and the description covers none of them. Query matching behavior, limit (default 10), and offset paging are all left for the agent to guess; the slug discussion is about results, not inputs.

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 ('Search the Infinite Backlog catalog') and enumerates the payload ('name, slug, year and category per hit'), so an agent knows exactly what it gets back. It does not name get_game as the sibling that consumes the slug, but the resource is unambiguous and distinct from the mutation tools in the catalog.

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?

'Use the slug with the other tools' positions this as the discovery entry point whose output feeds get_game and the add_* tools, which is real routing guidance. It gives no explicit when-not or fallback, but the context for calling it is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.