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 47 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. |
verbosity |
string | no | This tool has one size: compact is accepted and changes nothing (the response says so in a note). (full · compact) |
What comes back (declared outputSchema; fields marked required are always present):
| Field | Type | Required | Notes |
|---|---|---|---|
applied |
object | yes | |
current |
string | null | yes | |
docs |
string | yes | page or page#section for elixir_docs / elixir://docs. |
entries |
array | yes | |
meta |
object | yes | The envelope (docs: responses). |
next_offset |
number | null | yes | |
notes |
array | yes | One-sentence caveats to repeat when quoting the numbers. |
total |
number | null | yes |
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. |
verbosity |
string | no | This tool has one size: compact is accepted and changes nothing (the response says so in a note). (full · compact) |
What comes back (declared outputSchema; fields marked required are always present):
| Field | Type | Required | Notes |
|---|---|---|---|
docs |
string | yes | page or page#section for elixir_docs / elixir://docs. |
applied |
object | no | |
corpus_built_at |
string | null | no | |
fallback |
boolean | null | no | |
markdown |
string | null | no | |
matches |
array | no | |
meta |
object | yes | The envelope (docs: responses). |
notes |
array | yes | One-sentence caveats to repeat when quoting the numbers. |
pages |
array | no | |
query |
string | null | no | |
section |
string | null | no | |
section_slug |
string | null | no | |
slug |
string | null | no | |
title |
string | null | no | |
url |
string | null | no |
Examples elixir_examples
Ten worked examples of what people ask an agent connected to Elixir and what it answers: for players (understand your play, 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). |
verbosity |
string | no | This tool has one size: compact is accepted and changes nothing (the response says so in a note). (full · compact) |
What comes back (declared outputSchema; fields marked required are always present):
| Field | Type | Required | Notes |
|---|---|---|---|
docs |
string | yes | page or page#section for elixir_docs / elixir://docs. |
corpus_built_at |
string | null | yes | |
examples |
array | no | |
meta |
object | yes | The envelope (docs: responses). |
notes |
array | yes | One-sentence caveats to repeat when quoting the numbers. |
My feedback elixir_my_feedback
Your feedback and what happened to it: status (new/seen/planned/needs_info/done/declined), the maintainer's response, and ship links (shipped_in contract version, related_tools). needs_info is a question for you: reply with elixir_send_feedback follows_id. Every item you filed anywhere in Elixir is here. compact lists without bodies; feedback_id reads one item whole. Pages are bounded: pass next_offset as offset until null. Only responses delivered are marked seen. Poll only when meta.feedback_responses_pending says something is new.
Read-only ·
requires cr:read
| Argument | Type | Required | Notes |
|---|---|---|---|
feedback_id |
string | no | Read one of your items whole (11.10.0): message, response, refs, and the items that reply to it (followed_by) or name it as related (related_by). Its response is marked seen. The list filters are ignored. |
limit |
integer | no | |
offset |
integer | no | Pass the previous page's next_offset. |
status |
string | no | (new · seen · planned · needs_info · done · declined) |
since |
string | no | ISO instant; only items filed after this. |
area |
string | no | Only items about one part of Elixir (11.3.0): mcp, api, console, ladder, clan, mail, docs, recorder. (mcp · api · console · ladder · clan · mail · docs · recorder) |
verbosity |
string | no | compact: each item's id, created_at, area, category, title (the message's first line), status, follows_id, related_ids, has_response, responded_at and shipped_in, with no message or response bodies; nothing is marked seen. Read one whole with feedback_id. (full · compact) |
What comes back (declared outputSchema; fields marked required are always present):
| Field | Type | Required | Notes |
|---|---|---|---|
applied |
object | no | |
feedback |
array | yes | Newest first. verbosity compact (11.10.0) serves the listing fields only: title in place of message, has_response in place of response. |
total |
integer | yes | |
next_offset |
integer | null | yes | Pass as offset for the next page; null at the end. |
notes |
array | yes | One-sentence caveats to repeat when quoting the numbers. |
docs |
string | yes | page or page#section for elixir_docs / elixir://docs. |
meta |
object | yes | The envelope (docs: responses). |
Send feedback elixir_send_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, up to 8,000 characters. Specifics beat generalities. |
category |
string | no | data_quality: a fact looks wrong. judgment: Elixir judged someone wrongly (a standing, an award). (general · bug · data_quality · feature · praise · judgment · 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. Only your own calls attach. |
request_ids |
array | no | Beside request_id (3.18.0): every call this is about when a turn made several; the first becomes request_id when that was omitted, and all of them are kept with the report. |
refs |
array | no | Beside the calls (11.3.0): what else this is about. kind email (a send id from a mail's footer), feedback (one of your own feedback_ids this item belongs with, such as another facet of one review; not a reply, 11.10.0), player or clan (a tag), clan_action, award or policy (Elixir Clan ids). A pointer that is malformed or not yours is dropped and named in notes; the report is kept. |
follows_id |
integer | no | The feedback_id of your own item this follows (11.3.0), so the thread reads as one: a reply to an answer, the answer to a needs_info question, or a correction to something you filed. |
on_behalf_of |
string | no | Agent connections only: the person on your surface this feedback came from (e.g. discord:1234), when you relay theirs. Kept with the report so the maintainer sees it was theirs; the answer still comes to you. A personal connection is its person's, so it has no such argument. |
verbosity |
string | no | This tool has one size: compact is accepted and changes nothing (the response says so in a note). (full · compact) |
What comes back (declared outputSchema; fields marked required are always present):
| Field | Type | Required | Notes |
|---|---|---|---|
ok |
boolean | yes | |
feedback_id |
number | string | yes | |
category |
string | no | |
applied |
object | no | |
request_id |
string | no | |
request_ids |
array | no | |
docs |
string | yes | page or page#section for elixir_docs / elixir://docs. |
meta |
object | yes | The envelope (docs: responses). |
notes |
array | yes | One-sentence caveats to repeat when quoting the numbers. |
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 | |
verbosity |
string | no | This tool has one size: compact is accepted and changes nothing (the response says so in a note). (full · compact) |
What comes back (declared outputSchema; fields marked required are always present):
| Field | Type | Required | Notes |
|---|---|---|---|
docs |
string | yes | page or page#section for elixir_docs / elixir://docs. |
applied |
object | yes | |
corpus_built_at |
string | null | yes | |
entries |
array | yes | |
meta |
object | yes | The envelope (docs: responses). |
notes |
array | yes | One-sentence caveats to repeat when quoting the numbers. |
total |
number | null | yes |