Skip to main content
Glama

Workspace Management

workspace_manage
Destructive

Fastio workspaces (write): update settings, archive/unarchive, delete, import a share, create/update notes, delete QuickShare links, enable/disable cloud import. Destructive: delete (the workspace and all its files), quickshare-delete. Reads are on workspace. action='describe' gives the full action/param reference. Enabling Deep Indexing costs credits (10 per page); the toggle is rate-limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name (2-100 chars on update). Cannot be cleared.
actionYesOperation. Use 'describe' for full action reference.
blob_idNoBlob ID from POST /blob. Preferred for large note content (UTF-8 decoded). Single-use.
confirmNoMust match folder_name or numeric ID.
contentNoPlain text/markdown. Notes: max 102400 bytes (100 KiB) — use blob_id for larger.
node_idNoStorage tree node opaque ID. Both files and folders are nodes — use this name regardless of which.
blob_refNoAlias for blob_id (deprecated).
share_idNoShare ID or custom name: the share to import, or (read-note) the share holding the note.
note_nameNoNote filename (must end with .md).
parent_idNoParent folder opaque ID or 'root'.
perm_joinNoWho can join the workspace.
descriptionNoDescription. Newlines allowed. Send "null"/"" to clear on update.
folder_nameNoURL-safe workspace folder name (4-80 chars).
accent_colorNoBrand accent color JSON. "null" to clear.
workspace_idNoWorkspace opaque ID. Use this when only workspaces are valid (not shares or other contexts). For polymorphic contexts use profile_id. 19-digit numeric ID or custom name.
deep_indexingNoToggle Deep Indexing (AI indexing of file content). Enabling costs credits (10/page) to index existing files. Disable flushes embeddings; re-enable re-indexes. Rate-limited. Responses report it as `intelligence`.
display_limitNoHow 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, list-shares, members.
if_version_idNoCompare-and-swap base for update-note: the note's `version` from the read your edit was based on (read-note returns it as note.version). If the note has changed since, the update is rejected with a 409 version conflict naming the current version id, and nothing is changed. Omit for last-write-wins.
owner_definedNoCustom properties JSON. "null"/"" to clear.
sharing_sharesNoWhether new shares can be created here. Off blocks new ones only; the organization's setting is a ceiling.
cloud_sync_modeNoCloud sync direction ceiling: read (inbound only) or read_write. Not an on/off switch.
describe_actionNoWith action='describe': return one action's params and notes instead of the action index.
external_invitesNoThis workspace's external-invite switch; only tightens the organization's policy and cannot be reset to inherit.
background_color1NoBackground color 1 JSON. "null" to clear.
background_color2NoBackground color 2 JSON. "null" to clear.
perm_member_manageNoWho can manage members.
sharing_file_linksNoAs sharing_shares, for single-file share links.
metadata_extractionNoAutomatic metadata extraction for new uploads; effective only while Deep Indexing is on. Off deletes nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / cloud_sync_mode
      Added value: +{
      +  "description": "Cloud sync direction ceiling: read (inbound only) or read_write. Not an on/off switch.",
      +  "enum": [
      +    "read",
      +    "read_write"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / external_invites
      Added value: +{
      +  "description": "This workspace's external-invite switch; only tightens the organization's policy and cannot be reset to inherit.",
      +  "enum": [
      +    "allowed",
      +    "denied"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / if_version_id
      Added value: +{
      +  "description": "Compare-and-swap base for update-note: the note's `version` from the read your edit was based on (read-note returns it as note.version). If the note has changed since, the update is rejected with a 409 version conflict naming the current version id, and nothing is changed. Omit for last-write-wins.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / metadata_extraction
      Added value: +{
      +  "description": "Automatic metadata extraction for new uploads; effective only while Deep Indexing is on. Off deletes nothing.",
      +  "enum": [
      +    "true",
      +    "false"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Name. Send \"null\" to clear on update."New value: +"Display name (2-100 chars on update). Cannot be cleared."
    • changedInput schema / properties / share_id / description
      Previous value: -"19-digit numeric ID or custom name of share to import."New value: +"Share ID or custom name: the share to import, or (read-note) the share holding the note."
    • addedInput schema / properties / sharing_file_links
      Added value: +{
      +  "description": "As sharing_shares, for single-file share links.",
      +  "enum": [
      +    "true",
      +    "false"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / sharing_shares
      Added value: +{
      +  "description": "Whether new shares can be created here. Off blocks new ones only; the organization's setting is a ceiling.",
      +  "enum": [
      +    "true",
      +    "false"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / deep_indexing
      Added value: +{
      +  "description": "Toggle Deep Indexing (AI indexing of file content). Enabling costs credits (10/page) to index existing files. Disable flushes embeddings; re-enable re-indexes. Rate-limited. Responses report it as `intelligence`.",
      +  "enum": [
      +    "true",
      +    "false"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / intelligence
      Removed value: -{
      -  "description": "Toggle AI features. Enabling costs credits (10/page) to index existing files. Disable flushes embeddings; re-enable re-indexes. Rate-limited.",
      -  "enum": [
      -    "true",
      -    "false"
      -  ],
      -  "type": "string"
      -}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds useful specifics: delete removes the workspace and all its files, quickshare-delete is destructive, and enabling Deep Indexing costs 10 credits/page and is rate-limited. It does not cover auth requirements or confirmation behavior, but the added behavioral context is solid.

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?

The description is front-loaded and dense with useful information: it lists the write operations, flags destructive actions, names the read alternative, points to action='describe', and notes credit/rate-limit behavior. Every sentence earns its place with no filler.

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 complex 28-parameter action-based tool with no output schema, the description covers the main operation categories, destructive scope, read alternative, self-describe mechanism, and cost/rate-limit behavior. It is nearly complete, though it leaves permission and confirmation details to 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 28 parameters thoroughly. The description mentions action='describe' and the Deep Indexing credit/rate-limit behavior, but it does not add parameter-level syntax or meaning beyond what the schema 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 names the resource ('Fastio workspaces') and clearly frames the tool as the write/mutation surface, listing specific operations such as update, archive/unarchive, delete, import-share, and note management. It explicitly distinguishes itself from the sibling read tool by stating 'Reads are on `workspace`.'

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?

It states the primary usage context ('write') and names the read alternative (`workspace`). It also points to action='describe' for full action/param reference, but it does not explain when to choose each action or list prerequisites for actions like delete or quickshare-delete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources