Tools: Account
The Account tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Account
6 of the 55 tools in the registry. Generated from what tools/list returns, so this is exactly what your agent sees.
My players elixir_my_players
The players you track and WHO EACH ONE IS TO YOU: relationship (primary | alt | friend | watching), your private nickname if any, notify setting, recording status and current clan. That is what resolves "my alt" or "how are my friends doing" without asking. You do NOT need this to answer questions about yourself: omit player_tag and the tools already mean your primary.
Read-only ·
requires cr:read
Takes no arguments.
Nicknames elixir_nickname
Give a player YOUR nickname, private to your account and visible only to you and your agents ('to me Raquaza is Tyler'). Nicknames ride along wherever names appear (search matches them, summaries and rosters show them). Pass nickname: null to clear.
Changes state ·
requires account:write
| Argument | Type | Required | Notes |
|---|---|---|---|
player_tag |
string | yes | The tag to nickname, like #9L0V2QPC. |
nickname |
string | null | yes | Your name for them; null clears it. |
People you know elixir_my_identities
The humans you have learned, and which player each one is. Yours alone; one connection's mappings are invisible to every other. Useful for 'who am I to you?' and for spotting a mapping you got wrong.
Read-only ·
requires cr:read
Takes no arguments.
Track a clan elixir_track_clan
Track a clan on your account: starts recording in one act (tracked means recorded), within your tier's clan slots. scope activity records roster and war; comprehensive additionally records every member's battles and profile, following membership. action remove takes it off your account (recording stops when no account has it); notify_on / notify_off control whether it feeds your elixir_timeline.
Changes state ·
requires recordings:write
| Argument | Type | Required | Notes |
|---|---|---|---|
clan_tag |
string | yes | The clan tag, like #J2RGCRVG. |
action |
string | no | (add · remove · notify_on · notify_off) |
scope |
string | no | With add: activity records the clan itself; comprehensive additionally records every member. Tracking again with a different scope updates yours. (activity · comprehensive) |
Track a player elixir_track_player
Track a player on your account: claims the tag AND starts recording in one act (tracked means recorded), within your tier's player slots. Say who they are to you with relationship (primary = you, alt = also you, friend, watching); your first player becomes your primary. action remove releases the claim (recording stops if you were its only reason); notify_on / notify_off control whether the player feeds your elixir_timeline.
Changes state ·
requires recordings:write
| Argument | Type | Required | Notes |
|---|---|---|---|
player_tag |
string | yes | The tag, like #20JJJ2CCRU. |
action |
string | no | (add · remove · notify_on · notify_off) |
relationship |
string | no | Who this player is TO YOU: primary is you (exactly one; setting it on another tag moves it), alt is also you, friend is someone you follow, watching is everyone else (default). All four share your tier's player slots. (primary · alt · friend · watching) |
Who is asking elixir_identify
Remember which player a human is, so you never have to ask twice. An agent serves many people through one connection and MCP carries no per-request identity, so YOU supply one: discord:1234, signal:..., telegram:..., whatever your surface has. Pass that same id as on_behalf_of afterwards and 'how am I doing' resolves with no lookup. The mapping is yours alone and confers nothing (recorded reads are open to every account); it only picks a default subject. Call it once, right after they tell you who they are.
Changes state ·
requires account:write
| Argument | Type | Required | Notes |
|---|---|---|---|
external_id |
string | yes | The id this human has on your surface; namespace it however you like, it is opaque here. |
player_tag |
string | yes | The player they say they are. |