Fast.io

Destructive

Share management: create/update/delete, archive, password auth, members, autotitle. NOTE: quickshare-create is DEPRECATED (returns error 10756) — use the fileshare tool's create action for durable single-file shares. Call action='describe' for the full action/param reference. Destructive: delete (permanent). Side effects: autotitle AI-generates + applies a title/description (consumes credits, mutates share metadata). ⚠️ intelligence on create COSTS CREDITS (10/page) — default false unless user explicitly requests RAG. Verbosity (detail param): list/available/members default to terse (compact rows). public-details defaults to standard. details defaults to full (drill-down). Pass an explicit detail='terse'|'standard'|'full' to override.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Share title (2-80 chars; maps to API 'title').
`type`	No	Filter by share type.
`limit`	No	Internal backend page_size — stays MCP-internal so the platform cache stays warm. Use display_limit to control how many rows are actually returned. Forwarded by list/members.
`title`	No	Share title (2-80 chars). Alias of name.
`action`	Yes	Operation. Use 'describe' for full action reference.
`detail`	No	Per-entity verbosity for list/available/members/public-details/details. Defaults: terse for list/available/members, standard for public-details, full for details. See action='describe' for per-level field lists.
`expand`	No	quickshare-create only. Set to 'node' to include the full backend payload as a nested `node` field. Default response is slim: `{id, web_url, expires_at}`.
`invite`	No	Who can invite others (default: owners).
`notify`	No	Notification setting (default: never).
`offset`	No	Number of items to skip (default 0)
`org_id`	No	Filter shares to this org.
`confirm`	No	delete: must match the share's custom_name or id (validated client-side before the call).
`expires`	No	Expiration: 'YYYY-MM-DD HH:MM:SS' for create/update; seconds (default 10800, max 604800) for quickshare-create.
`node_id`	No	Storage tree node opaque ID. Both files and folders are nodes — use this name regardless of which. File node opaque ID. Quickshares: single file, max 1 GB, default 3h, max 7 days.
`password`	No	Password (only with 'Anyone with the link').
`share_id`	No	Share profile ID or custom name.
`room_goal`	No	REMOVED — Coordination Rooms were deleted from the platform on 2026-08-25 and this parameter no longer does anything. Supplying it is REFUSED rather than ignored, so a stale tool list cannot silently drop your value. Do not use it.
`expires_at`	No	ISO 8601 datetime for quickshare expiration.
`share_type`	No	New share type.
`custom_name`	No	Custom share URL name (4-80 chars; Unicode letters, digits, hyphens, underscores). Omit to have one auto-generated.
`description`	No	Share description (10-500 chars).
`folder_name`	No	Name for new folder (default: 'Shared Folder').
`accent_color`	No	Accent color as JSON string.
`display_type`	No	Display mode (default: grid).
`intelligence`	No	Enable RAG indexing. ⚠️ COSTS CREDITS (10/page) — default false unless user requests it. Forced false on workspace_folder shares.
`storage_mode`	No	Storage mode (default: independent).
`user_context`	No	autotitle only: optional user-provided context to guide the AI-generated title/description.
`workspace_id`	No	Workspace opaque ID. Use this when only workspaces are valid (not shares or other contexts). For polymorphic contexts use profile_id. Parent workspace ID.
`create_folder`	No	Create a new workspace folder (workspace_folder mode).
`display_limit`	No	How many items to return. Default 10, max 500. The MCP trims post-fetch; backend page_size stays MCP-internal so the platform cache stays warm. Applies to list.
`owner_defined`	No	Custom metadata as JSON string.
`access_options`	No	Access level. 'Anyone with the link' not allowed for receive/exchange.
`folder_node_id`	No	Workspace folder node ID (workspace_folder mode).
`describe_action`	No	When action='describe', narrow the output to ONE action's full params/notes (e.g. 'create'). Omit to get the compact action index.
`workspace_style`	No	Use workspace styling (default: true).
`background_image`	No	Background image index (0-128, default 0).
`comments_enabled`	No	Enable comments (default: true).
`background_color1`	No	Primary background color as JSON string.
`background_color2`	No	Secondary background color as JSON string.
`download_security`	No	Download security: off (default), medium (no guest download), high (block all guest downloads).
`guest_chat_enabled`	No	Enable guest chat (default: false).
`anonymous_uploads_enabled`	No	Allow guests to upload anonymously on public Receive/Exchange shares.

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it flags delete as permanent, discloses that autotitle consumes credits and mutates share metadata, warns that intelligence costs credits (10/page) and defaults to false, and explains per-action verbosity defaults. No contradiction with the annotations.

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?

Dense but well-organized: purpose first, then deprecation warning, self-reference to describe, destructive semantics, side effects, cost warning, and verbosity defaults. Every sentence carries operational value, and the warnings are visually flagged.

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 a 42-parameter, multi-action tool with no output schema, the description covers deprecation, cost, destructive behavior, side effects, and verbosity defaults, and provides an action='describe' escape hatch for further detail. It is not fully self-contained regarding return values, but that is a reasonable deferral for such a complex tool.

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%, and the schema itself already documents key behaviors like credit costs, removed parameters, and limit/display_limit semantics. The description reinforces cost and verbosity defaults but adds little parameter-level meaning beyond what the schema already provides.

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?

The description opens with 'Share management: create/update/delete, archive, password auth, members, autotitle' — a specific, verb-rich inventory of operations rather than a tautology. It also names the sibling tool fileshare as the replacement for the deprecated quickshare-create, helping distinguish this tool from related siblings.

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?

The description explicitly routes agents away from deprecated quickshare-create toward fileshare's create for durable single-file shares, and directs agents to call action='describe' for the full action/param reference. It doesn't enumerate every possible alternative sibling, but the critical routing decision is covered clearly.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool covers a clearly distinct domain (auth, storage, shares, comments, events, AI, etc.), and overlapping concepts like share vs. fileshare are explicitly disambiguated with deprecation notes and cross-references. An agent can reliably select the correct tool for a task without ambiguity.

Naming Consistency3/5

Tool names are all lowercase single words, but they mix nouns (user, org, workspace) with verbs (download, find, upload) and include a hyphenated 'how-to'. There is no consistent verb_noun or noun-only pattern, though the names are still readable and memorable.

Tool Count4/5

19 tools is slightly above the typical 3-15 sweet spot, but the platform's breadth (auth, file management, sharing, collaboration, AI, metadata, and help) justifies this count. Each tool represents a substantial domain area, so none feel redundant.

Completeness5/5

The toolset provides full lifecycle coverage for the platform: authentication, user/org/workspace management, file storage/upload/download/search, sharing (both quickshare and durable file shares), comments, events, metadata pipelines, AI assistance, and product help. No obvious dead ends or missing operations are apparent.

Resources

Need Help?