Skip to main content
Glama

Fast.io

by io.fast.mcp
OverviewDiscussionsAdmin

Download

download
Read-onlyIdempotent

Download URLs for files (file-url) and folder ZIPs (zip-url), and details of existing QuickShare links (quickshare-details, deprecated; new links are created on fileshare_manage). Consumes bandwidth credits. action='describe' gives the full action/param reference.

Input Schema

NameRequiredDescriptionDefault
actionYesOperation. Use 'describe' for full action reference.
node_idNoStorage tree node opaque ID. Both files and folders are nodes — use this name regardless of which.
share_idNoAlias for profile_id when the profile is a share — implies profile_type=share (so profile_type may be omitted).
context_idNoAlias for profile_id (either name works)
profile_idNoPolymorphic context ID. Pair with profile_type=workspace|share. Typed aliases let you omit profile_type: workspace_id (⇒ workspace) / share_id (⇒ share); also context_id / instance_id. 19-digit profile ID or custom name.
version_idNoSpecific file version ID.
instance_idNoAlias for profile_id (REST/how-to name; profile_id is canonical).
context_typeNoAlias for profile_type (either name works)
profile_typeNoProfile type.
workspace_idNoAlias for profile_id when the profile is a workspace — implies profile_type=workspace (so profile_type may be omitted).
quickshare_idNoQuickshare opaque identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / profile_id / description
      Previous value: -"Polymorphic context ID. Pair with profile_type=workspace|share. Typed aliases let you omit profile_type: workspace_id (⇒ workspace) / share_id (⇒ share); also…"New value: +"Polymorphic context ID. Pair with profile_type=workspace|share. Typed aliases let you omit profile_type: workspace_id (⇒ workspace) / share_id (⇒ share); also context_id / instance_id. 19-digit profile ID or custom name."
  2. Changed3 schema fields changed
    • changedInput schema / properties / profile_id / description
      Previous value: -"Polymorphic context ID. Pair with profile_type=workspace|share|org. Use workspace_id instead when only workspaces are valid. 19-digit profile ID or custom name."New value: +"Polymorphic context ID. Pair with profile_type=workspace|share. Typed aliases let you omit profile_type: workspace_id (⇒ workspace) / share_id (⇒ share); also…"
    • addedInput schema / properties / share_id
      Added value: +{
+  "description": "Alias for profile_id when the profile is a share — implies profile_type=share (so profile_type may be omitted).",
+  "type": "string"
+}
    • addedInput schema / properties / workspace_id
      Added value: +{
+  "description": "Alias for profile_id when the profile is a workspace — implies profile_type=workspace (so profile_type may be omitted).",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / instance_id
      Added value: +{
+  "description": "Alias for profile_id (REST/how-to name; profile_id is canonical).",
+  "minLength": 1,
+  "type": "string"
+}
  4. Changed7 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Operation to perform"New value: +"Operation. Use 'describe' for full action reference."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "file-url",
-  "zip-url",
-  "quickshare-details"
-]New value: +[
+  "describe",
+  "file-url",
+  "zip-url",
+  "quickshare-details"
+]
    • changedInput schema / properties / node_id / description
      Previous value: -"Storage node opaque ID (required for: file-url, zip-url)"New value: +"Storage tree node opaque ID. Both files and folders are nodes — use this name regardless of which."
    • changedInput schema / properties / profile_id / description
      Previous value: -"19-digit workspace or share ID, or custom name (also accepted as context_id) (required for: file-url, zip-url)"New value: +"Polymorphic context ID. Pair with profile_type=workspace|share|org. Use workspace_id instead when only workspaces are valid. 19-digit profile ID or custom name."
    • changedInput schema / properties / profile_type / description
      Previous value: -"Profile type: \"workspace\" or \"share\" (also accepted as context_type) (required for: file-url, zip-url)"New value: +"Profile type."
    • changedInput schema / properties / quickshare_id / description
      Previous value: -"Quickshare opaque identifier (required for: quickshare-details)"New value: +"Quickshare opaque identifier."
    • changedInput schema / properties / version_id / description
      Previous value: -"Version ID for a specific file version (used by: file-url)"New value: +"Specific file version ID."
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely new context: it consumes bandwidth credits and flags quickshare-details as deprecated. It does not describe URL expiry or output shape, so not a 5.

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

Conciseness4/5

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

Front-loaded with the core capability, then the deprecation caveat, then the cost and the describe pointer in a compact two-sentence block. Dense but every clause carries information; slightly telegraphic phrasing costs it a point.

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 11-parameter tool with no output schema, the description covers the action space, the credit cost, the deprecation status, and a discovery escape hatch via describe. It omits return-value/URL-lifetime details, but annotations carry the safety profile and the schema carries parameter detail.

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 already documents the polymorphic profile_id aliases, node_id, and version_id in detail. The description only repeats the action-value names, adding little beyond what the schema provides, so baseline 3 applies.

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 a specific verb (download) plus the exact resources returned (file URLs, folder ZIPs) and maps the action enum values file-url/zip-url/quickshare-details to those outcomes. It also distinguishes itself from the sibling fileshare_manage for link creation, so an agent can tell it apart without inspecting schemas.

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 clear context for each action and explicitly routes quickshare link creation to fileshare_manage, plus points to action='describe' for the full reference. It lacks explicit when-not-to-use guidance versus read siblings like find or storage, so it falls just short of a 5.

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

All Fast.io toolsInspect
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