Adapter Details: venue

Public effective venue settings, plus venue-owned administration to enable, disable and reconfigure adapters, load or unload modules, garbage-collect the store, or restart the standalone process.

Name:venue
Class:covia.adapter.VenueAdapter

MCP Tools

This adapter provides 9 MCP tool(s) for AI agent integration:

Tool NameDescription
venue_restartGracefully closes every venue in this JVM and hands off to a successor executable Covia jar. The requesting Job is completed and persisted before shutdown. A helper waits for the old JVM to exit, starts the successor, and starts the current jar as a fallback if the successor does not signal readiness. Omit jar to restart the current version. Venue-owned: requires venue/restart on <venue DID>/process.
venue_module-unloadUnloads a module from the running venue: removes live adapters and v/info entries, closes resources and its classloader, and leaves durable catalog metadata in place. Requires dynamicModules.enabled. In-flight jobs on its adapters fail at their next point of use; JVM class unloading is best-effort. Not persisted across restarts — a boot-declared module returns on restart. Venue-owned: requires adapter/manage on <venue DID>/adapters.
venue_adapter-enableEnables a disabled adapter on the running venue: overwrites its catalog declarations, publishes its v/info/adapters entry and resumes dispatch. Idempotent (changed is false when already enabled). Not persisted across restarts. Venue-owned: requires adapter/manage on <venue DID>/adapters.
venue_gcCollects the venue's Etch store while the venue keeps serving: everything reachable from the lattice root is copied into a fresh file and the venue cuts over to it, with reads and writes continuing throughout. The superseded file is deleted when the venue next closes (or on the following start if the platform still pins it), and the collected file is adopted under the store's name on the next start — so disk comes back at shutdown unless restart is set. One collection per process: a second needs a restart first (etch.gc.onStart collects at boot). Needs free disk of about the current file size. Venue-owned: requires venue/gc on <venue DID>/store; restart additionally requires venue/restart on <venue DID>/process.
venue_module-loadLoads an adapter module jar into the running venue. Its adapters and catalog declarations overwrite existing names and paths. Requires dynamicModules.enabled; by default the module must be a jar name inside the staging directory dynamicModules.dir (no absolute paths or '..'); dynamicModules.anyPath widens this to any filesystem path. Optional sha256 pins the jar content. The live module is not persisted across restarts. Venue-owned: requires adapter/manage on <venue DID>/adapters.
venue_adapter-configureApplies a new effective configuration to a registered adapter (active or disabled) on the running venue — the same shape as the adapters.<name> config block. Replaces the effective config unless merge is true. The adapter may reject the settings, in which case nothing changes. Not persisted across restarts. Venue-owned: requires adapter/manage on <venue DID>/adapters.
venue_show-configReturns a curated public view of effective venue settings that agents and clients need to operate correctly: venue identity, agent defaults, job/audit policy, storage durability, access and protocol availability, limits, validation mode, active adapters, and each adapter's explicitly allow-listed public settings. This is not the raw operator config: private paths, network allow-lists, module details, credentials and secret references are never included.
venue_adapter-disableDisables an active adapter on the running venue: removes its v/info/adapters entry and stops dispatch while leaving durable catalog metadata in place. The kernel marker is informational and does not restrict venue authority. In-flight jobs finish on the retained instance. Idempotent; not persisted across restarts. Venue-owned: requires adapter/manage on <venue DID>/adapters.
venue_adaptersLists every registered adapter on this venue — active and disabled — with its kernel flag, owning module, effective configuration and operations, plus the loaded modules. Venue-owned: requires adapter/manage on <venue DID>/adapters.

Navigation

Back to all adapters

Back to index