Fast.io

File Share Management

fileshare_manage

Destructive

Fastio File Shares (write): create a durable share link bound to one workspace file (immutable binding), update, delete, and add/revoke per-user grants (grant-by-email creates a pending invite for an unregistered address). Destructive: delete (removes the share, not the file), grant-revoke. Reads are on fileshare. action='describe' gives the full action/param reference.

Input Schema

TableJSON Schema

Name	Required	Description
`node`	No	create: the workspace file node ID to bind (immutable).
`user`	No	grant-add/grant-revoke: grantee user ID. Exactly one of user/email.
`email`	No	grant-add/grant-revoke: grantee email. Exactly one of user/email. An unregistered email becomes a pending invite.
`title`	No	Human-readable share title. create / update.
`action`	Yes	Operation. Use 'describe' for full action reference.
`expires`	No	create/update: relative expiry in SECONDS from now (1..3155760000). Mutually exclusive with expires_at.
`password`	No	create/update: sets the share password ('' on update clears it).
`capability`	No	grant-add: view \| download \| edit (ordered); edit allows content write-back.
`expires_at`	No	create/update: absolute expiry 'YYYY-MM-DD HH:MM:SS UTC'. Exclusive with expires. update: '' clears it.
`fileshare_id`	No	File Share ID.
`workspace_id`	No	Parent workspace ID.
`access_option`	No	Access tier (create/update). A tier never confers `edit`; that needs an explicit edit grant.
`comments_enabled`	No	create/update: allow comments on the File Share (create default: off). Always off on anyone_with_link shares.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

addedInput schema / properties / comments_enabled

Added value: +{
+  "description": "create/update: allow comments on the File Share (create default: off). Always off on anyone_with_link shares.",
+  "type": "boolean"
+}

AddedOct 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark this destructive/openWorld, but the description adds non-obvious behavior the booleans cannot convey: delete removes the share and not the file, the file binding is immutable, and grant-by-email to an unregistered address creates a pending invite. These are exactly the operational nuances an agent needs before calling a destructive tool.

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 sentences, front-loaded with the write scope and destructive actions, no filler. The action/param reference is delegated to `describe` instead of bloating the description with 13 parameters.

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

Completeness5/5

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

Thirteen parameters are fully documented in the schema, annotations carry the safety profile, and there is no output schema to explain. The description fills the remaining gaps (destructive semantics, sibling routing, describe escape hatch), so nothing an agent needs to invoke correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100% and each parameter already documents its own constraints (enums, exclusivity, expiry ranges). The description restates a couple of these (immutable binding, pending invite) rather than adding syntax the schema lacks, but its framing of grants and access tiers gives useful orientation. Slightly above the baseline-3 case for full coverage.

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?

Names a specific verb set (create/update/delete/grant-add/grant-revoke) on a specific resource (Fastio File Shares), and explicitly scopes it as the write side by pointing reads to the `fileshare` sibling. An agent can distinguish it from `fileshare`, `share_manage`, and `workspace_manage` without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes reads to `fileshare`, flags exactly which actions are destructive (delete, grant-revoke), and offers `action='describe'` as the lookup path for the full reference. This covers when-to-use, when-not-to-use, and the alternative in three compact clauses.

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?