Tools: Help
The Help tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Help
6 of the 55 tools in the registry. Generated from what tools/list returns, so this is exactly what your agent sees.
Changelog elixir_changelog
What changed in the tool CONTRACT since a version (client tool schemas cache aggressively). Entries after since, newest first, with tools_added and breaking notes; omitted since starts at the newest release. Pages default to 20 entries: pass next_offset as offset until it is null to read the complete history. elixir_updates is the product-level list written for people.
Read-only ·
requires cr:read
| Argument | Type | Required | Notes |
|---|---|---|---|
since |
string | no | Contract version you last saw (any response's meta.contract_version). Omit to page through the full changelog. |
limit |
integer | no | Release entries per page. |
offset |
integer | no | Pass the previous page's next_offset; keep since unchanged. |
Documentation elixir_docs
Elixir MCP's own documentation, the same pages a person reads at elixir.poapkings.com/docs. No arguments: the index (every page with its section, lede and sections). page: one page's Markdown; page + section: one H2 section. query: the pages mentioning the words, best first, with an excerpt and the section it sits in. Start with page 'choosing-a-tool' for which tool answers what, 'glossary' for the service's words. The tool reference itself is tools/list.
Read-only ·
requires cr:read
| Argument | Type | Required | Notes |
|---|---|---|---|
page |
string | no | A page slug from the index (e.g. choosing-a-tool, glossary, battles, clocks, recording, agents, limits). |
section |
string | no | With page: one H2 section, by its slug or title as the index lists them. |
query |
string | no | Words to search for across every page; ignored when page is given. |
Examples elixir_examples
Eleven worked examples of what people ask an agent connected to Elixir MCP and what it answers: for players (understand your play, pick a deck, push with evidence, follow friends), clan leaders (win the river race, keep the roster healthy, scout the other clan, write the weekly recap) and builders (answer clanmates in Discord, publish your own stats, run a collector). No arguments: the index. example: one in full with its transcript, what it reads, the tools it calls and the setup. The numbers inside a transcript are illustrative; the tools are real.
Read-only ·
requires cr:read
| Argument | Type | Required | Notes |
|---|---|---|---|
example |
string | no | An example slug from the index (e.g. play, clan, discord). |
My feedback elixir_my_feedback
Your feedback and what happened to it: status (new/seen/planned/done/declined), the maintainer's response, and ship links (shipped_in contract version, related_tools). Results are bounded pages: pass next_offset as offset until null. Only responses delivered on this page are marked seen. Poll only when meta.feedback_responses_pending says something is new.
Read-only ·
requires cr:read
| Argument | Type | Required | Notes |
|---|---|---|---|
limit |
integer | no | |
offset |
integer | no | Pass the previous page's next_offset. |
status |
string | no | (new · seen · planned · done · declined) |
since |
string | no | ISO instant; only items filed after this. |
Send feedback elixir_feedback
File feedback with the maintainer ON YOUR OWN JUDGMENT; your user never needs to ask. File when a capability you needed is missing, a workflow took more calls than it should, a result confused or misled you, data looked wrong, or something delighted you enough to protect. Consolidated end-of-session feedback beats a stream. Every item gets a response (elixir_my_feedback), often with a shipped_in version.
Changes state ·
requires feedback:write
| Argument | Type | Required | Notes |
|---|---|---|---|
message |
string | yes | The feedback itself. Specifics beat generalities. |
category |
string | no | (general · bug · data_quality · feature · praise · other) |
context |
string | no | Which tool or question prompted this (e.g. 'battles_query pagination'). |
request_id |
string | no | The meta.request_id of the call this is about. Every response carries one; passing it here attaches the exact request, its arguments and its answer to the report, so the maintainer can see what you saw. Prefer this over describing the call in words. |
What's new elixir_updates
What's new on Elixir MCP: every user-visible change, newest first, as written for people at elixir.poapkings.com/updates. Distinct from elixir_changelog (the tool contract version by version). since: entries on or after a date; limit: how many.
Read-only ·
requires cr:read
| Argument | Type | Required | Notes |
|---|---|---|---|
since |
string | no | YYYY-MM-DD; entries from that day on, newest first. |
limit |
integer | no |