Skip to main content
Glama

videogames

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. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds substantial behavioral context: sources_failed vs sources_used semantics, USPTO soft-fail via sunset, empty sections meaning real 'no data,' and private-company resolved:false behavior. It also clarifies expected absence of FDA products for non-biologic companies, preventing false failure interpretation.

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 it is front-loaded with trigger phrases and the most critical usage rule, and the dense middle section earns its place by documenting numerous source-specific quirks. A little redundancy exists around the interchangeable 'type' behavior, but overall it is organized and information-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?

Given no output schema, the description thoroughly covers the return shape, each data section, source failure behavior, input formats, and edge cases like private companies. An agent has enough context to call this tool correctly and interpret unexpected or empty results without needing additional documentation.

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 coverage is already 100%, and the description enriches both parameters by giving concrete examples, explaining zero-padded CIK format, and emphasizing that 'type' values are interchangeable. This goes beyond the schema without duplicating its definitions.

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 natural-language triggers and the core action: 'full cross-source profile of a US public company in ONE parallel call.' It names the resource (SEC EDGAR, XBRL, USPTO, USAspending, FDA, DOL, GDELT, GLEIF) and clearly distinguishes itself from single-pack lookup chains, making the tool's identity unambiguous.

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?

It explicitly instructs 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' It also clarifies when to expect a non-failure result for private companies and states that both 'company' and 'ticker' type values behave identically, giving the agent actionable routing and handling guidance.

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

All videogames 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

Heavy overlap within the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta which is currently identical, ask_pipeworx_grounded, deep_research) and among prediction market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) makes selection genuinely ambiguous. Some tools are distinct (remember/recall/forget), but the clustering blurs boundaries.

Naming Consistency2/5

Conventions are mixed: some tools use verb_noun (list_games, get_game, filter_games, subscribe, unsubscribe, recall, remember) while others use ad-hoc noun phrases or brand-style names (polymarket_arbitrage, entity_profile, deep_research, ask_pipeworx, bet_research). No single pattern dominates, making it harder to predict tool names.

Tool Count1/5

34 tools is heavy, and the mismatch is severe: the server is named 'videogames' but only 3 of 34 tools (list_games, get_game, filter_games) have any relation to video games. The bulk are Pipeworx data/prediction-market/memory utilities that do not belong under this server's apparent purpose. This is a fundamental scope failure.

Completeness2/5

As a video game server, the surface is extremely thin: only list/get/filter by tags and platform, with no search by name, no CRUD, no reviews, no categories beyond the fixed filter set. The other 31 tools are irrelevant to the videogames domain, so the stated purpose is largely uncovered. The mismatch makes coverage assessment nearly impossible for the actual server name.

Resources