Skip to main content
Glama

Bungie

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.9/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds key behavioral traits: fans out across two services, first measurement can take 5-30s, partial failures degrade gracefully with sources_failed listed. No contradiction 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?

Single, well-structured paragraph with every sentence adding value. Front-loaded with core purpose, then details on services, use cases, limitations, and edge cases. No 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?

Despite no output schema, description comprehensively lists return fields (summary block, per-advisory, links, alternatives). Covers input constraints, behavior, failure modes, and timing. Sufficient for agent to understand and invoke 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?

Schema coverage is 100% with descriptions for both parameters. Description adds context: scoped packages accepted for 'package', and 'version' defaults to latest if omitted. This extra context raises value above baseline 3.

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 performs a composite check for adding an npm package, combining deps.dev and bundlephobia data. It distinguishes from siblings by specifying the exact scope and services involved.

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 states when to use (agent asks about safety/popularity/size/cost) and provides alternatives for other ecosystems (PyPI, Maven, etc. via deps.dev:version). Also mentions partial failure behavior.

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

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

C2.7/5.0
Disambiguation3/5

The tool set mixes Destiny 2 game tools with a large suite of general data querying tools from Pipeworx. Within the data querying subset, tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research have overlapping purposes, making it hard for an agent to distinguish which to use. The Destiny tools are more distinct, but overall, the set has noticeable ambiguity.

Naming Consistency2/5

Tool names are highly inconsistent, mixing single-word names (character, clan), snake_case (ask_pipeworx, deep_research), and compound names with underscores (polymarket_arbitrage, scan_dependency). There is no uniform verb_noun or other predictable pattern, making it difficult for an agent to infer functionality from the name alone.

Tool Count2/5

With 43 tools, the server is bloated for its stated name 'Bungie'. Many tools are unrelated to Bungie (e.g., Pipeworx data tools, Polymarket tools), suggesting the server aggregates multiple domains without clear scoping. The tool count is too high for a coherent set focused on a single service.

Completeness2/5

For the Bungie game domain, the set is fairly complete (characters, clans, stats). However, the inclusion of numerous unrelated tools (financial, economic, prediction market) fragments completeness. The server lacks a clear domain, leaving gaps in both the Bungie-specific and the general data querying aspects when considered as a unified set.

Resources