destiny2-mcp git:20261008.f8dcc3eA

Immutable. This exact content never changes and is served at /api/v1/blob/fb5a8cb317b07c1b.

---
name: destiny2-mcp
description: Use when a task involves the local Destiny 2 MCP - player profile, inventory and item lookup, weapon and perk questions, armor or build recommendations, saved loadouts, subclass and artifact state, activity history, weekly resets and vendors. Covers which tool and intent to call with which parameter, how to tell account data from Manifest and community data, and the confirmation rules for account writes.
metadata:
  short-description: Route Destiny 2 MCP queries safely across agents
---

# Destiny 2 MCP

This is a platform-neutral usage guide. An agent may read this file directly from a local copy or from GitHub; it does not require any host-specific skill installation.

## First decision: what evidence does the user want?

- Player/account state, owned items, current rolls, or saved loadouts: use an account-aware intent.
- All game definitions or possible rolls: use the Manifest/catalog intent; this does not prove ownership.
- Community explanations or tables: use the relevant `community` intent; results can come from bundled author Markdown or an optional local web archive and are not official recommendations or live search.
- Community builds require the optional archive and a returned `community_build_id`. The bundled Markdown contains reference material and weapon recommendations, not complete character builds.
- A write such as move, equip, save, delete, or modify: read the current state first, show the exact target, and wait for explicit confirmation before sending `confirmed=true`.

Read only the relevant reference before a complex request:

- [routing.md](references/routing.md) for the per-tool intent index, the parameter rules, community categories, and the rating scales.
- [evidence-and-completeness.md](references/evidence-and-completeness.md) for scope, pagination, missing data, and warnings.
- [community-builds.md](references/community-builds.md) for Starside templates and inventory matching.
- [account-loadouts.md](references/account-loadouts.md) for local and Bungie official loadouts.
- [execution-safety.md](references/execution-safety.md) before any operation that can change game or local account state.

## Non-negotiable boundaries

1. Never infer account ownership from Manifest results, community templates, or a previous conversation.
2. Never call `loadout_assistant` to answer a community-build question.
3. Never call `catalog` to answer what the player owns; use `filter_rolls` or an account inventory query.
4. `build_template`, community records, `farm_options`, and `solver_handoff` are not executable builds —
   but **`solver_handoff.arguments` is exactly what you pass to `find`** (copy it verbatim; it already
   dropped names this Manifest cannot resolve, so a `null` set bonus is deliberate).
5. Only a server-returned, instance-bound candidate may be sent to `equip_build`: either its
   `canonical_build` or its scalar `execution_id`. Never assemble hashes or instance IDs yourself.
   A build that needs tuning carries the tuning plugs inside `canonical_build.items[].mods`
   (only the tunings that piece allows), so a confirmed `equip_build` changes them together
   with the armor and mods — tell the player what `tuning_changes` says before they confirm,
   and never claim a target is unreachable while a returned build meets it.
6. If a response is incomplete, failed, or has an uncertainty/coverage warning, report that limitation instead of filling it from model memory.
7. A parameter the chosen `intent` does not read is rejected with `ignored_parameter`; switch to the intent named in the message instead of retrying the same call.
8. The `community` intent of `weapon`, `build`, `subclass` and `activity` searches only its own category. A zero result there does not mean the archive lacks the topic; retry with `world_assistant(intent="community")` and name the category searched.
9. Hosts that can only send scalar arguments (the Doubao connector does this) write list and map
   parameters as text (`"亡者复仇,速射"`, `"grenade=100"`) and use `execution_id` instead of the
   nested `canonical_build`. The shapes are listed in `references/routing.md`; a wrong shape comes
   back as `invalid_arguments` with an example, never as a silently narrowed request.

## Installation handoff

This file explains usage, not platform registration. Follow the repository's `README.md` and `skills/destiny-mcp-setup/SKILL.md` for installation and OAuth.

Nothing here assumes a particular host: any agent that can read Markdown can use this file directly, from a local copy or from the repository. Hosts with a skills directory load the whole folder; hosts that only read an instruction file can be pointed at `references/routing.md`; hosts that only speak MCP already receive the essentials plus the online guide address in the server's handshake instructions.