Skip to main content
Glama

Thegamesdb

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

Schema Changelog

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

  1. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readoly/open-world/idempotent/non-destructive, so the safety profile is covered. The description adds substantial behavioral context beyond that: multi-source fan-out, source-specific failure modes (USPTO soft-fail), empty-section semantics ('real no data, not a bug'), and resolved:false behavior for private companies. This is exactly the kind of context an agent needs.

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 long but front-loaded with purpose and trigger phrases, then organized source-by-source with semicolons. Every source and caveat earns its place given the complexity. Minor redundancy exists with schema text around type/value interchangeability, but overall it is dense rather than padded.

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?

There is no output schema, so the description must carry the burden of explaining return values. It does so thoroughly: it enumerates all returned sections, source fallbacks, failure modes, and edge cases. An agent calling this tool would know what to expect and how to interpret an empty or partially failed response.

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?

Schema description coverage is 100%, so the baseline is 3. The description still adds value by clarifying that value can be a ticker, zero-padded CIK, or company name, and that type is interchangeable. It also flags the name-resolution behavior and private-company outcome, which helps the agent understand parameter consequence.

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 opens with concrete user-intent examples and states a specific verb+resource: "full cross-source profile of a US public company in ONE parallel call." It also distinguishes itself from narrower lookups by instructing agents to prefer this over chaining single-pack SEC/XBRL/news lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' which is clear when-to-use guidance. It also tells the agent how to disambiguate inputs (ticker, zero-padded CIK, company name) and what to expect for private companies, covering edge cases that affect invocation.

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