Skip to main content
Glama

Thegamesdb

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds value beyond annotations by stating the output format: 'top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly.' This provides behavioral detail that annotations alone do not convey.

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?

The description is a single paragraph that front-loads the core purpose and includes every necessary detail. It could be more structured (e.g., bullet points) but no sentence is wasted, earning above average conciseness.

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?

Given the 6 parameters, no output schema, and many sibling tools, the description is complete. It covers purpose, usage, output format, and parameter behavior, providing a full picture for an agent to use the tool correctly.

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

Parameters4/5

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

With 100% schema coverage, the baseline is 3. The description adds value by clarifying the alias parameters (q, task, search, description) and the default limit, reinforcing parameter usage beyond what the schema already provides.

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?

The description clearly states 'Find tools by describing the data or task' and lists many specific domains, establishing a specific verb+resource. It distinguishes itself from sibling tools as the discovery tool.

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?

The description explicitly says 'Use when you need to browse, search, look up, or discover what tools exist' and advises 'Call this FIRST when you have many tools available and want to see the option set.' It provides clear usage context but does not explicitly state when not to use it or give alternative tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

ask_pipeworx and ask_pipeworx_beta are explicitly described as functionally identical right now, creating direct ambiguity. The six polymarket tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread, bet_research) have blurred boundaries for prediction-market tasks, and ai_visibility_check vs scan_competitor_ai_presence is a wrapper relationship. Only the memory trio and subscription lifecycle are cleanly distinct.

Naming Consistency2/5

Naming follows multiple conventions with no global pattern: bare verbs (remember, recall, forget, subscribe), product-prefixed verbs (ask_pipeworx, pipeworx_feedback), noun phrases (entity_profile, deep_research, recent_changes), and verb_noun snake_case (discover_tools, validate_claim). There are consistent pockets (the polymarket_* family, the TheGamesDB get_/list_/search_ verbs), but the overall mix across 35 tools is inconsistent.

Tool Count2/5

35 tools exceeds the 25-tool threshold for a heavy server, and the count is wildly disproportionate to the server's stated identity: only 4 of 35 tools relate to TheGamesDB while 31 belong to an unrelated Pipeworx data/prediction-market suite. The game database would justify roughly 5-10 tools, so the bulk of this surface is out of scope for the server name.

Completeness3/5

The Pipeworx portion is genuinely thorough — discovery, grounded querying, entity resolution, claim validation, subscription lifecycle, memory, and feedback form a coherent coverage. However, the namesake TheGamesDB surface is thin: search, get-by-id, list genres, and list platforms, with no games-by-platform/genre browsing, no media/screenshots beyond front boxart, and no updates feed. The set as a whole covers multiple unrelated domains with no single complete lifecycle.

Resources