historical_stats_for_accountFetch account-wide aggregated Destiny 2 historical stats across all characters for a membership_type + destiny_membership_id.
| Name | Required | Description | Default |
|---|---|---|---|
| membership_type | Yes | ||
| destiny_membership_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety. Description adds context about account-wide aggregation but lacks details on authentication, rate limits, or data freshness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with verb and resource, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With output schema present, return values need not be explained. Description covers what is fetched and how to identify the account. Could add membership type values, but still adequate for a simple fetch tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so description should compensate. It only mentions parameter names without explaining what 'membership_type' (e.g., platform codes) or 'destiny_membership_id' represent, adding minimal semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Fetch account-wide aggregated Destiny 2 historical stats', specifying verb, resource, and scope. Differentiates from sibling 'historical_stats' by emphasizing account-wide aggregation across all characters.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'historical_stats'. No mention of prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.