Skip to main content
Glama

videogames

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

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

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses rich behavioral details: source fan-out (SEC EDGAR, GDELT→GNews fallback), rate-limit fallback logic, USPTO soft-fail due to PatentsView sunset, and return structure (changes[], total_changes, citation URIs). No contradictions with annotations.

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?

The description is dense but every sentence adds value, from user-facing examples to source details to output summary. It is well-structured, front-loaded with the query patterns the tool answers, and avoids fluff.

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?

The description fully covers the tool's complexity: multiple data sources, fallback behavior, date parsing, output shape, and alternative tool link. Since there is no output schema, the description adequately explains return values and identifiers.

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 already covers 100% of parameters, but the description adds extra semantics: it explains `since` accepts ISO or relative shorthand with examples, recommends typical values, and clarifies `value` can be ticker or CIK. This goes beyond the schema's basic descriptions.

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 the tool's function with specific verbs and resources: it provides a change feed for a company over a time window, with examples ('What's new with X'). It distinguishes from the sibling entity_profile tool by contrasting dynamic changes with static profiles.

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?

Explicit guidance is given: mentions typical use ('Use 30d or 1m for typical monitoring') and names an alternative ('Use entity_profile instead when you want the static profile'). This clearly signals when to use this tool vs alternatives.

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