Provides native access to internal services in this Covia venue, including lattice read/write/list/delete for user data.
| Name: | covia |
| Class: | covia.adapter.CoviaAdapter |
This adapter provides 8 MCP tool(s) for AI agent integration:
| Tool Name | Description |
|---|---|
| covia_slice | Read a paginated slice from a collection at any lattice path. For vectors: array of elements; for maps: array of {key, value}. Use after covia_list reveals a large collection. Example: g/Alice/timeline limit=5 (recent agent runs). |
| covia_delete | Delete a value at a writable lattice path (w/, o/, n/, t/). Example: w/scratch/temp-data (clean up workspace). Idempotent — deleting a non-existent path is a no-op. |
| covia_read | Read a value from any lattice path. Examples: w/vendor-records/acme (workspace data), v/ops/covia/write (operation metadata), did:key:<id>/w/shared (cross-user read). Returns {exists, value}. For large values use covia_list to check size first, covia_slice for pagination, or covia_inspect for a budget-controlled summary. |
| covia_append | Append an element to a vector at a writable path (w/, o/, n/, t/). Creates the vector if it doesn't exist. Example: w/audit/trail (build an immutable event log). Errors if the target is not a vector — use covia_write to replace non-vector values. |
| covia_copy | Copy a value from any readable path to any writable path. Key use: pin a venue op as a named shortcut — covia_copy from=v/ops/json/merge to=o/merge, then grid_run operation=o/merge. Also useful for snapshotting data or branching workspace values. Both read and write capability checks apply. |
| covia_inspect | Primary discovery tool. Budget-bounded JSON5 preview of any lattice path: shows shape, types, sizes, and partial values without overwhelming context. Annotations like {/* +15 more, 102KB */} reveal what was elided so you can decide where to drill in next. All paths resolve under your DID as the implicit root. Two kinds of sub-namespaces: Venue-virtual (read-only, same view for every caller — start here for discovery): v/ops/ venue operation catalog (e.g. v/ops/json/merge) v/info/ venue introspection (adapters, capabilities) Your private namespaces (start empty; populated by your writes): w/ workspace — read/write structured data o/ operation pins — short names for grid_run a/ content-addressed assets — immutable blobs by hash g/ agents — config, state, timeline, inbox n/ named references t/ transient/scratch space j/ job log — auto-populated by the venue as you invoke ops Federated: did:key:<id>/ another user's namespace (subject to access control) did:web:<host>/ another venue Note: '/' lists only your materialised entries (j/ and anything you've written) — virtual namespaces like v/ resolve on lookup but don't appear in root enumeration. So begin with covia_inspect path=v. Progressive exploration: covia_inspect path=v budget=400 (venue overview) → covia_inspect path=v/ops/secret budget=2000 (drill down) → covia_read path=v/ops/secret/set (full value when ready). Pass an array of paths to compare multiple values in one call. |
| covia_list | List keys at a lattice path with pagination. Returns type, count, and a (paginated) key array — values are not fetched. Use when you need just the keys of a known map (e.g. iterating agents under g/) or when paginating a large collection. For discovery and exploration use covia_inspect, which is budget-bounded and shows shape and sample values in one call. covia_slice paginates values; this paginates keys. |
| covia_write | Write a value to a writable lattice path (w/, o/, n/, t/). Examples: w/enrichments/INV-001 (persist a work product), o/my-pipeline (pin an operation for grid_run). Intermediate maps are created on demand. Writing null deletes the entry. Use structured values (objects/arrays) rather than serialised strings. |