Alloy

Read the edge client's current configuration. Two modes: - `path=None` → full manifest (every config file + content). - `path="state.json"` (or any path) → that single file's raw content. A full-manifest response contains every configuration file and its content. A single-file response contains the current raw content for `path`.

get_edge_config

Return the public edge release manifest. Lists every available Docker distro, architecture, variant, and tag, plus every available binary release. The response contains public release metadata and no secrets.

get_edge_manifest

Resolve a Mesh Storage file locator to concrete files. Provide exactly one locator: - `paths`: one or more mesh-relative file paths, no `uploads/` prefix. - `mission_id`: exact match on `mesh.file_meta` key `alloy.mission_id`. - `metadata_filters`: exact key/value matches against `mesh.file_meta`, for example `[{"key": "alloy.mission_id", "value": "mission-123"}]`.

list_mesh_files

List Iceberg table names in the org's Mesh Storage, or search columns. Discovery is filtered and paginated because an organization can have more than 1,000 tables. - `name_filter`: case-insensitive substring on the table name, e.g. `name_filter="battery"` returns every `*battery*` table. - `column_filter`: case-insensitive substring searched across column AND struct field names in every table. For example, `column_filter="heading"` returns `{schema, table, column, matched_fields}` rows like `fleet, statecsv__data, data, ["Heading_degrees"]`; select matched fields double-quoted (`data."Heading_degrees"`). `name_filter` and `column_filter` can be combined. - `limit` (default 25, max 1000) + `offset` page the results; when more tables remain, the response includes `next_offset`.

list_mesh_tables

List every device registered to the org with health + storage stats. Use this to answer "what devices do I have", "which are pending approval", "when did device X last sync", or "how many files has each device uploaded". One call returns edge_id, device_id, status (approved / pending / rejected), last_seen_at, last_upload_at, file_count, total_size_bytes, and pending_key_roll.

list_devices

Preview a small bounded page from one Mesh Storage table. This operation accepts one table and optional simple column names. It does not accept arbitrary SQL, expressions, or joins.

preview_mesh_table

Run read-only DataFusion SQL over the org's Mesh Storage Iceberg tables. Mesh SQL uses fully qualified `alloy.*` Iceberg tables and supports read-only SELECT and WITH queries. It is not DuckDB MCAP SQL; forms such as `$FILE` and `read_mcap_*` functions are unsupported. Results are bounded by `limit` and `offset`, including SQL without a LIMIT clause. Mission, exact `file_id`, and time-range predicates can reduce fleet scans before aggregates, sorts, list expansion, or payload retrieval. A natural `alloy.mesh.file_meta` join on `file_id` can dynamically prune fleet files. Supported top-level and primitive struct-leaf predicates can prune files when metrics exist. Struct containers, list or map descendants, and pointer payloads cannot prune files. The result `limit` bounds output, not scan or blocking-operator work. List indexes are 1-based. Bracket access after a list-of-struct index has the form `data.points[1]['x']`. Full list expansion has the form `CROSS JOIN UNNEST(t.data.items) AS u(item)`. Correlated expansion is inner, accepts one list expression, and requires an alias. Null and empty lists produce no rows. Correlated `JOIN UNNEST ... ON`, outer expansion, `WITH ORDINALITY`, multi-argument correlated UNNEST, and arbitrary correlated LATERAL subqueries are unsupported. Ordinary table joins remain supported. Supported large binary leaves such as `data.data` or `data.image.data` may be pointer-backed. Project the exact leaf after selective inline filters; `SELECT *` or the parent struct does not request nested payload hydration. Pointer-backed payload contents are not filterable. Engine validation, syntax, unsupported-form, and scan-budget failures are returned in `error`. Transport and Arrow-stream failures can be transient or can represent a late query/data error after streaming begins. A selective query can be retried once after a transport or stream failure; repeated failures require a narrower or simpler query.

query_mesh_storage

Reject a pending device. No API key is ever issued.

reject_device

Search Alloy product docs, or read a specific page.

search_docs

Write a single edge config file. Overwrites if it already exists. This operation replaces the full content at `path`. The edge client picks up changes on its next sync, normally within 60 seconds, and restarts the recorder atomically. For `state.json`, omitted process entries are removed from the running process list.

update_edge_config