Clan
clanRead-onlyIdempotent
Clan/group detail.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Bungie
TDQS
D1.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations clearly indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the agent knows this is a safe, idempotent read operation. The description adds no extra behavioral detail (e.g., rate limits, auth), but does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short (4 words), but lacks necessary information. While concise in length, it sacrifices completeness, making it insufficient for an agent to understand the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has one parameter and an output schema, but the description fails to convey what the output represents or how to use the tool effectively. The context is incomplete for a simple lookup tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one required string parameter 'group_id' with no description. Schema coverage is 0%, and the tool description does not explain the parameter's meaning or format, forcing the agent to guess.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Clan/group detail.' identifies the resource but lacks a verb (e.g., 'get' or 'retrieve') and does not specify what kind of detail is provided. The sibling tool 'clan_members' suggests differentiation, but the description does not distinguish itself.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. There is no indication of when to use this tool versus alternatives like 'clan_members' or 'entity_profile', leaving the agent without context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
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.