Tools & resources
Every tool the agent can call, every resource it can read, and the guided prompts it can run.
This page lists everything the agent can use: the tools it calls to take action, the resources it reads to ground itself, and the prompts that guide it through common tasks.
In the tool tables, the Access column marks each tool Read or Write. Write tools change files or control generators, and are gated: over HTTP they require server.mcp.allow_write, and over stdio they are available unless you pass --read-only.
Discovery tools
Read-only, and available on both transports. They let the agent learn what Eventum offers before it writes a config.
| Tool | Description |
|---|---|
list_plugins | List the available input, event, and output plugins. |
get_plugin_schema | Return the configuration schema for one plugin. |
list_formatters | List the available output formatters. |
get_formatter_schema | Return the configuration schema for one formatter. |
describe_sample | Describe a CSV or JSON sample file used by a generator. |
list_secret_names | List the secret names in the keyring, so a config can reference them. The agent cannot read or change their values — that is done with eventum-keyring. |
list_secret_references | List what reads a given secret — the projects whose configuration reads it, and the connected repositories authenticating with it — to see what a rename or a removal would break. |
Workspace & authoring tools
Available on both transports. They operate on the generators in your generators directory.
| Tool | Access | Description |
|---|---|---|
list_generators | Read | List the saved generators. |
list_generator_files | Read | List the files in one generator. |
read_generator_file | Read | Read a file in a generator. A file larger than the read limit comes back in windows the agent pages through, so a generator output file cannot flood its context. |
write_generator_file | Write | Create or overwrite a file in a generator. |
delete_generator_file | Write | Delete a file from a generator. |
delete_generator | Write | Delete a whole generator and its files. |
export_generator | Read | Pack a whole generator into a ZIP archive. Named top-level entries can be left out, which is how generated output stays behind. |
import_generator | Write | Create a generator from a ZIP archive. An archive that wraps the generator in directories imports the same way as one holding it at the top level. |
validate_generator | Read | Validate a generator and return any errors. |
preview_timestamps | Read | Preview the timestamps a generator would produce. |
preview_events | Read | Preview the events a generator would produce. |
run_generator | Write | Run a saved generator once to its configured outputs, stopping when it finishes or reaches a time or event limit. |
validate_generator and the preview_* tools load the generator into the same pipeline a real run uses, so the agent sees exactly what a run would produce. See how it works.
An archive travels inside the tool call, so it lands in the agent's context. An agent that can make HTTP requests and write files is better off taking the archive from the REST API instead, which moves it as a file and carries a project of any size. export_generator and import_generator say so themselves, and refuse an archive over 128 KiB, where the REST API is the only route left.
Repository tools
Available on both transports. They read the connected repositories of the instance — git repositories that publish ready-made generators — and install what one of them publishes into your generators directory.
| Tool | Access | Description |
|---|---|---|
list_repositories | Read | List the connected repositories, each with whether it answered the last time it was asked. The password of a private repository comes back as the secret it references, or as *** when the value is kept in the repositories file itself. |
discover_repositories | Read | List the repositories that publish generators in the open, so the agent can name one for the user to connect. The content of a listed repository is not reviewed. |
get_repository_catalog | Read | List the generators one repository publishes — what each of them produces, what it consists of, and the projects it is already installed as. Reads the repository anew on request. |
install_generator | Write | Install a published generator as a project of the generators directory. An existing project is never overwritten. |
Connecting and disconnecting repositories is deliberately not exposed: it names credentials and decides what the instance trusts. Do it on the Repositories page of Studio, or in the repositories file itself. Over stdio the agent reads that same file — repositories.yml next to the generators directory, or the one --repositories names.
Live-management tools
Available only over HTTP. They control the generators the server manages, and rename the objects an instance holds.
| Tool | Access | Description |
|---|---|---|
list_generators_live | Read | List the generators the server manages, with their status. |
get_generator_status | Read | Return the current status of one managed generator. |
get_generator_stats | Read | Return runtime statistics for one running generator, including the resources it occupies. |
start_generator | Write | Start a managed generator. |
stop_generator | Write | Stop a managed generator. |
register_generator | Write | Register an authored generator with the running server, so it can be started and is restored after a server restart. |
unregister_generator | Write | Remove a generator from the running server, and stop restoring it on restart. |
rename_generator | Write | Rename a stopped generator, keeping its project, parameters and scenario membership. |
get_generator_logs | Read | Return the recent log lines for a managed generator, to diagnose a run. |
list_startup_generators | Read | List the generators configured to start with the server. |
rename_generator_config | Write | Rename a project, moving its directory and repointing the generators that use it. All of them must be stopped first. |
rename_secret | Write | Rename a secret, keeping its value under the new name. Everything referring to it follows — the ${secrets.*} token is rewritten in each project configuration, and connected repositories authenticating with it are repointed. Refused when a repository already authenticates with the new name. |
Scenario tools
Available only over HTTP. A scenario is a named group of generators — a tag on their startup entries — used to operate related generators together.
| Tool | Access | Description |
|---|---|---|
list_scenarios | Read | List the defined scenarios. |
get_scenario | Read | Return a scenario and the ids of the generators in it. |
add_generator_to_scenario | Write | Add a generator to a scenario. |
remove_generator_from_scenario | Write | Remove a generator from a scenario. |
rename_scenario | Write | Rename a scenario, rewriting the tag on every generator in it. |
delete_scenario | Write | Delete a scenario, untagging every generator in it. |
Global-state tools
Available only over HTTP. Generators coordinate at runtime through a shared global state; these tools read and edit it. The values are runtime data written by templates and are returned as-is.
| Tool | Access | Description |
|---|---|---|
get_global_state | Read | Return the whole shared global state. |
get_global_state_key | Read | Return one value from the global state. |
set_global_state | Write | Set one or more keys in the global state. |
delete_global_state_key | Write | Remove one key from the global state. |
clear_global_state | Write | Remove every key from the global state. |
Instance tools
Available only over HTTP. They read and control the running instance itself.
| Tool | Access | Description |
|---|---|---|
get_instance_logs | Read | Return the recent log lines of one log channel of the instance — its core, the server, the requests it served, or this MCP server. |
update_settings | Write | Patch the instance settings file. Auth credentials cannot be changed, and the change applies on the next restart. |
stop_instance | Write | Stop the instance. |
restart_instance | Write | Restart the instance, applying any pending settings change. |
The MCP server runs inside the instance, so stop_instance and restart_instance end the agent's own connection — the call returns as the server goes down.
Resources
Documents the agent reads to ground itself. Read-only, on both transports.
| Resource | Description |
|---|---|
eventum://templating/reference | The in-template API the template plugin exposes, always current with the installed version. |
eventum://schema/generator | The JSON Schema of the top-level generator.yml document. |
eventum://examples/generators | Bundled, validated worked examples to start from, plus links to the public content-packs repository and the generator hub. |
eventum://workspace/configs | The generators currently saved in your generators directory. |
eventum://instance/info | Version, runtime, and host metrics of the running instance. HTTP only. |
eventum://instance/settings | The running instance settings, with auth credentials redacted and absolute paths reduced to file names. HTTP only. |
Prompts
Ready-made task guides the agent can invoke.
| Prompt | Description |
|---|---|
create_generator | Guide the agent through the full authoring loop. |
live_ops | Operate the generators on a running server. HTTP only. |