linked_profilesFetch all cross-platform Destiny 2 profiles linked to a Bungie.net membership_id/membership_type; optionally return all memberships including inactive ones.
| Name | Required | Description | Default |
|---|---|---|---|
| membership_id | Yes | ||
| membership_type | Yes | ||
| get_all_memberships | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "get_all_memberships": true,
+ "membership_id": "4611686018429783292",
+ "membership_type": 3
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Cross-platform profiles response",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, open-world, idempotent, non-destructive behavior. The description adds context about cross-platform profiles and optional inactive memberships, but does not disclose additional behavioral traits such as error conditions or rate limits.
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?
The description is a single, front-loaded sentence. It efficiently conveys the main action and key option, though it could be trimmed without loss of meaning.
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?
Given the tool's simplicity and strong annotations, the description is functionally adequate but lacks example use cases or explanation of what 'linked profiles' entails. The optional parameter is mentioned, but not fully contextualized.
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?
With 0% schema description coverage, the description mentions 'membership_id/membership_type' and the optional flag, but fails to explain acceptable values for membership_type or the effect of get_all_memberships. Basic meaning is conveyed, but insufficient for full agent understanding.
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?
The description uses a specific verb ('Fetch') and resource ('cross-platform Destiny 2 profiles linked to a Bungie.net membership_id/membership_type'), clearly distinguishing it from sibling tools like 'profile' or 'search_destiny_player' by focusing on linked profiles.
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?
The description mentions the optional parameter to include inactive memberships, but lacks explicit guidance on when to use this tool versus alternatives (e.g., when to prefer 'profile' for a single profile). No comparison or exclusions are provided.
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.