Fast.io

Organization Management

org_manage

Destructive

Fastio organizations (write): create, update, workspaces, billing, members, invitations, assets. Destructive: close (org and all data), billing-cancel, remove-member, leave, transfer-ownership, invitation-delete, asset-delete. Reads are on org.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Display name (3-100 chars).
`role`	No	Org role: `member` or `admin`. `owner` is not assignable; `guest`/`view` are workspace/share roles, rejected (1605).
`email`	No	Invitee email.
`state`	No	Invitation state, e.g. pending, accepted.
`action`	Yes	Operation; 'describe' lists the actions.
`domain`	No	Subdomain: lowercase alphanumeric and hyphens, globally unique, not reserved.
`org_id`	No	Organization 19-digit ID or domain string.
`confirm`	No	Org domain or ID, confirming close.
`content`	No	Plain-text asset body, e.g. SVG.
`expires`	No	Updated expiration datetime.
`message`	No	Invitation message (10-255 chars).
`user_id`	No	User ID.
`industry`	No	Industry key (see industry-list).
`metadata`	No	Asset metadata as a JSON array string.
`file_name`	No	File name, e.g. logo.png.
`member_id`	No	Member user ID or email.
`perm_join`	No	Permission level required to join workspace.
`asset_name`	No	Asset name, e.g. "logo", "banner".
`description`	No	Description (10-1000 chars).
`file_base64`	No	Base64 binary asset content.
`folder_name`	No	Workspace folder name (4-80 chars).
`join_action`	No	Accept or decline the invitation (default accept).
`permissions`	No	Updated permission level.
`twitter_url`	No	Twitter/X URL.
`youtube_url`	No	YouTube URL.
`accent_color`	No	Brand accent color as JSON.
`billing_plan`	No	Plan ID, e.g. solo_monthly; billing-plans lists current IDs. The free plan is closed to new subscriptions.
`content_type`	No	MIME type (default application/octet-stream).
`facebook_url`	No	Facebook URL.
`homepage_url`	No	Website URL.
`billing_email`	No	Billing contact email.
`deep_indexing`	No	Deep Indexing (RAG indexing), 10 credits per page. Default "false". Responses report it as `intelligence`.
`instagram_url`	No	Instagram URL.
`invitation_id`	No	Invitation ID or invitee email.
`owner_defined`	No	Owner-defined properties as JSON.
`invitation_key`	No	Invitation key from invite link.
`use_background`	No	Show the background: "true" or "false".
`background_mode`	No	Background mode, e.g. 'stretched', 'fixed'.
`describe_action`	No	With action='describe': return one action's params and notes instead of the action index.
`background_color`	No	Background color as JSON.
`background_color1`	No	Primary background color as JSON.
`background_color2`	No	Secondary background color as JSON.
`perm_member_manage`	No	Who can manage members, e.g. 'Owner only'.
`metadata_extraction`	No	Automatic metadata extraction for new uploads (default "true"); effective only while Deep Indexing is on.
`perm_authorized_domains`	No	Authorized email domain for auto-join.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

addedInput schema / properties / metadata_extraction

Added value: +{
+  "description": "Automatic metadata extraction for new uploads (default \"true\"); effective only while Deep Indexing is on.",
+  "enum": [
+    "true",
+    "false"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / deep_indexing

Added value: +{
+  "description": "Deep Indexing (RAG indexing), 10 credits per page. Default \"false\". Responses report it as `intelligence`.",
+  "type": "string"
+}

removedInput schema / properties / intelligence

Removed value: -{
-  "description": "RAG indexing, 10 credits per page. Default \"false\".",
-  "type": "string"
-}

AddedOct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, but the description adds real value by naming which actions are destructive and spelling out the worst consequence (close destroys the org and all data). It does not cover auth/permission requirements or rate limits. Note the tool does expose a `describe` read action even though the text says reads live on `org` — a minor inconsistency, not an annotation contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight clauses with zero filler: scope first, capability families second, destructive actions third, sibling routing last. Every phrase earns its place in a tool whose schema carries the bulk of the detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-action, 45-parameter tool with no output schema, the description covers the high-risk information (which actions destroy data) and the read/write split. It omits mention of the `describe` mechanism and the `confirm` requirement for close, though both are fully documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 45 parameters with constraints, enums, and cross-references (billing-plans, industry-list). The description adds no parameter-level detail beyond grouping the actions, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource (Fastio organizations) and the scope (write) and enumerates the operation families it covers: create, update, workspaces, billing, members, invitations, assets. It explicitly distinguishes itself from the read sibling by naming `org` as the read path, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear routing rule — writes here, reads on `org` — and flags the destructive subset, which tells the agent when caution is required. It stops short of stating when a write should be avoided entirely or what prerequisites (e.g. confirm for close) gate each action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fast.io tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?