Tools: Live

The Live tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.

‹ All tools

Live

1 of the 47 tools in the registry. Generated from what tools/list returns, so this is exactly what your agent sees.

Live CR API fetch live_fetch

The catch-all: one allowlisted raw GET against the CR API through the live lane (per-account daily quota, spends the shared CR budget). It stores nothing: the payload comes back to you and never enters the record. Paths: /players/{tag}, /clans/{tag}, /clans/{tag}/currentriverrace, /clans/{tag}/riverracelog; /players/{tag}/battlelog is refused (too large): use battles_query({ live: true }). Prefer the recorded tools, which take live: true. RAW payload: card levels are the API's rarity-relative scale.

Read-only · requires cr:read · reaches the live Clash Royale API, outside the record

ArgumentTypeRequiredNotes
path string yes e.g. /players/#20JJJ2CCRU or /clans/#J2RGCRVG/currentriverrace
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):

FieldTypeRequiredNotes
applied object no
live_status object no state fresh with fetched_at, or matchmaking (a currentriverrace read of a race not yet matched after a season roll: no race yet) with fetched_at and retry_after_s.
payload 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.
Something wrong on this page?

Help for Tools: Live

The Live tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.

Read more

The page you are on rides along. Every item is answered, and the answer comes to your email and your timeline.