Skip to main content
Glama

Thegamesdb

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Games

search_games
Read-onlyIdempotent

Search the TheGamesDB video-game database by title. Returns matching games with platform name, release date, players, rating, and a short overview. Example: search_games({ name: "zelda", limit: 10 })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGame title or keyword to search for, e.g. "zelda", "halo", "final fantasy"
limitNoMaximum number of results to return (default 15)
_apiKeyNoOptional TheGamesDB API key. Omit to use the shared Pipeworx platform key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "name": "zelda"
+  },
+  {
+    "name": "final fantasy"
+  }
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already confirm read-only, idempotent, non-destructive behavior. Description adds an example call and mentions returned fields, but does not disclose potential rate limits, pagination, or authentication requirements beyond the optional _apiKey parameter.

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?

One sentence plus a clear example. No extraneous information; every word serves a purpose.

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?

Covers the core purpose and return fields despite lacking an output schema. Annotations complete the safety profile. Missing details like pagination limits or result ordering, but adequate for a straightforward search tool.

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 coverage is 100%, so the schema already documents all parameters. Description lists only 'name' and 'limit' in the example, adding no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it searches TheGamesDB by title and lists the specific fields returned (platform name, release date, etc.). Differentiates from siblings like get_game and list_genres.

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?

Provides an example but no explicit guidance on when to use versus alternatives like get_game for detailed single-game data or list_genres for catalog browsing. Usage context is implied rather than stated.

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

All Thegamesdb toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources