Skip to main content
Glama

Bungie

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent. Description adds beyond: scoping, behavior when key omitted, and relationship to siblings. No contradictions.

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?

Concise, front-loaded with core action. Every sentence adds value with no waste.

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?

Complete for a simple read tool with good annotations. Covers purpose, usage, scoping, and sibling relationships.

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 has 100% coverage with description of key. Description adds that omitting key lists all saved keys, which is critical usage info beyond 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?

Clearly states the tool retrieves a value saved via remember or lists all keys when no key is provided. Uses specific verb+resource and distinguishes from siblings like remember and forget.

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

Usage Guidelines4/5

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

Explicitly says when to use (look up stored context) and mentions scoping and pairing with remember/forget. Lacks explicit when-not-to-use, but context is sufficient.

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