Skip to main content

MCP tool reference: administration

Tools that administer an account: the administration feeds, settings, users and scopes, reached as operations through the admin dispatchers (describe_operations lists them). They need the floxar.admin capability, which only an Admin's grant carries. This page is generated from the tools as Floxar's MCP server registers them, so names, inputs and descriptions match what your client receives. See also reading content and running trails and authoring content.

Every tool answers with the same envelope: on success, success: true and the result in data; on failure, an error result whose error has a code, a message and an errorId to quote when reporting a problem. The rules every call follows — the lock token, the trail keys (optional: derived from the ids when omitted), the intent key, scope, paging and the envelope — are stated on the fields that need them and returned in full by describe_platform as rules; see also Connecting an AI client.

administer_operation​

Administer Operation. Only for operations that have no tool of their own; list them with describe_operations. Runs one admin-class write (account administration under floxar.admin; never a dangerous act, which has a tool of its own) by its dispatch_id. Take dispatch_id from a describe_operations listing, never a guessed one. Send the REST path parameters in path_params, the query parameters in query and the request body in body, under the REST names the contract lists. A keyed operation takes client_intent_id, a UUID v4 you mint per write; resend the identical call after an ambiguous failure and the repeat answers the committed outcome (_meta.deduplicated true). Answers the REST body under data with _meta naming the operation. A trail-family write, a keyless write and a dangerous act are never dispatched and are refused naming their tool; an operation of another class or kind is refused OPERATION_NOT_DISPATCHABLE naming its dispatcher; one a core tool covers is refused USE_TOOL naming the tool.

  • Capability: floxar.admin
  • Permission level: Admin
  • Behaviour: writes
InputTypeRequiredDescription
bodyobjectnoThe REST request body by its REST member names (the contract's request_body).
client_intent_ididnoIntent key — send a fresh UUID v4 on every write; mint it before the call. If the outcome is ambiguous (timeout, transport error) resend the identical call with the same id: the repeat answers the committed outcome (deduplicated: true), never a second write. Only where the operation's contract (describe_operations) says keyed; sent under the row's key field for you. A row that is not keyed refuses it.
dispatch_idstringyesThe operation's dispatch id as describe_operations lists it: its operationId, or operationId.variant for a per-class split.
path_paramsobjectnoThe REST path parameters by their REST names (the contract's parameters with in: path), one value each.
queryobjectnoThe REST query parameters by their REST names (the contract's parameters with in: query), as the query string carries them: a string, number or boolean, or a list sent as one comma-separated string. Never accountId: the bound account is injected.

Returns: _meta.

read_admin_operation​

Read Admin Operation. Only for operations that have no tool of their own; list them with describe_operations. Runs one admin-class read (administration feeds and the Admin-only reads, under floxar.admin) by its dispatch_id. Take dispatch_id from a describe_operations listing, never a guessed one. Send only the parameters the task asks for: each optional filter in the contract narrows the result. Send the REST path parameters in path_params and the query parameters in query, under the REST names the contract lists. Answers the REST body under data (its data and meta members) with _meta naming the operation. A read below Admin belongs to read_operation and is refused OPERATION_NOT_DISPATCHABLE naming it; an operation a core tool covers is refused USE_TOOL naming the tool.

  • Capability: floxar.admin
  • Permission level: Admin
  • Behaviour: read-only, idempotent
InputTypeRequiredDescription
dispatch_idstringyesThe operation's dispatch id as describe_operations lists it: its operationId, or operationId.variant for a per-class split.
path_paramsobjectnoThe REST path parameters by their REST names (the contract's parameters with in: path), one value each.
queryobjectnoThe REST query parameters by their REST names (the contract's parameters with in: query), as the query string carries them: a string, number or boolean, or a list sent as one comma-separated string. Never accountId: the bound account is injected.

Returns: _meta.

Last reviewed: 2026-10-22

Last updated on