Skip to main content
Glama

Gaming Feeds

by io.github.pipeworx-io

Scan Dependency

scan_dependency
Read-onlyIdempotent

Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesnpm package name. Scoped packages (e.g. "@types/node") are accepted.
versionNoSpecific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted.

TDQS

A4.6/5.0
Behavior5/5

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

Description adds behavioral details beyond annotations: fans out to two external services, potential latency (5-30s), graceful degradation via sources_failed, and return structure. Annotations already indicate read-only and idempotent, which are consistent.

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?

Description is relatively lengthy but every sentence adds value for a complex composite tool. Front-loaded with main purpose and usage, then technical details. No redundancy.

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 adequately explains all return information: summary block, advisory details, links, alternative versions. Covers ecosystem restriction and partial failure behavior.

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?

Input schema has 100% coverage with clear parameter descriptions (package name with scoped packages, version defaults to latest). Description does not add extra parameter-level semantics beyond the schema.

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 it is a composite check for npm packages, aggregating data from deps.dev and bundlephobia, and distinguishes from other tools by specifying ecosystem scope.

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?

Explicitly tells when to use: when an agent asks about safety, popularity, size, or cost of adding a package. Also specifies not to use for other ecosystems (PyPI, Maven, etc.) and directs to alternate tool usage.

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

All Gaming Feeds 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

A4.1/5.0
Disambiguation3/5

Most tools have distinct purposes, but there is notable overlap among ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research—all of which route questions to the same underlying catalog. The polymarket_* family also has several opportunity-scanning tools (edges, arbitrage, bet_research) that agents could confuse without reading the long descriptions carefully.

Naming Consistency5/5

All 34 tool names use lowercase snake_case with a clear verb-first or noun-descriptive pattern (list_feeds, read_feed, remember, resolve_entity, polymarket_arbitrage). Even compound names like ai_visibility_check and ask_pipeworx_grounded follow a predictable, consistent style. No mixed conventions or camelCase deviations.

Tool Count2/5

34 tools is far more than the apparent 'Gaming Feeds' scope suggests—only list_feeds, read_feed, and fetch_feed actually relate to gaming feeds. The rest form a sprawling data-research and prediction-market suite, creating a severe mismatch between the server name and its actual tool surface.

Completeness4/5

Viewed as a general Pipeworx data-access platform, the tool set is quite complete: question routing, grounded answers, entity resolution, profiles, comparisons, claim validation, memory, subscriptions, alerts, feed reading, and tool discovery are all covered. The only notable gaps are feed management (no create/update/delete for custom feeds) and a few odd add-ons like generate_llms_txt that feel outside the core domain.

Resources