Fast.io

Member

member

Read-only

Fastio workspace and share members (read): list (active and pending), details. Writes are on member_manage.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of items to return (1-500, default 100)
`action`	Yes	Operation; 'describe' lists the actions.
`offset`	No	Number of items to skip (default 0)
`user_id`	No	User profile ID (share).
`entity_id`	No	Workspace or share ID (19-digit numeric or custom name). Must match entity_type.
`member_id`	No	Member ID (workspace).
`entity_type`	No	Workspace or share.
`display_limit`	No	How many members the list action returns (default 10, max 500), trimmed after the fetch.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 3, 2026

changedInput schema / properties / action / description

Previous value: -"Operation. Use 'describe' for full action reference."New value: +"Operation; 'describe' lists the actions."

changedInput schema / properties / action / enum

Previous value: -[
-  "describe",
-  "list",
-  "add",
-  "remove",
-  "details",
-  "update",
-  "transfer-ownership",
-  "leave",
-  "join",
-  "join-invitation"
-]New value: +[
+  "describe",
+  "list",
+  "details"
+]

changedInput schema / properties / display_limit / description

Previous value: -"How many members to return for the list action. Default 10, max 500. The MCP trims post-fetch; backend paging stays MCP-internal so the platform cache stays warm."New value: +"How many members the list action returns (default 10, max 500), trimmed after the fetch."

removedInput schema / properties / email_or_user_id

Removed value: -{
-  "description": "Email (to invite) or user ID (to add directly).",
-  "type": "string"
-}

removedInput schema / properties / expiration

Removed value: -{
-  "description": "Alias for expires (share only).",
-  "type": "string"
-}

removedInput schema / properties / expires

Removed value: -{
-  "description": "Membership expiration — `YYYY-MM-DD HH:MM:SS UTC` for BOTH workspace and share. ISO 8601 is NOT accepted (406).",
-  "type": "string"
-}

removedInput schema / properties / force_notification

Removed value: -{
-  "description": "Force notify existing user (workspace-only).",
-  "type": "boolean"
-}

removedInput schema / properties / invitation_action

Removed value: -{
-  "description": "Accept or decline.",
-  "enum": [
-    "accept",
-    "decline"
-  ],
-  "type": "string"
-}

removedInput schema / properties / invitation_expires

Removed value: -{
-  "description": "Invitation expiration ISO 8601 (workspace-only).",
-  "type": "string"
-}

removedInput schema / properties / invitation_key

Removed value: -{
-  "description": "Invitation key string.",
-  "type": "string"
-}

removedInput schema / properties / message

Removed value: -{
-  "description": "Invitation email message (10-255 chars).",
-  "maxLength": 255,
-  "minLength": 10,
-  "type": "string"
-}

removedInput schema / properties / notifications

Removed value: -{
-  "description": "Notification preference (workspace string).",
-  "type": "string"
-}

removedInput schema / properties / notify_options

Removed value: -{
-  "description": "Notification preference (share).",
-  "type": "string"
-}

removedInput schema / properties / permissions

Removed value: -{
-  "description": "Workspace permission level.",
-  "enum": [
-    "admin",
-    "member",
-    "guest"
-  ],
-  "type": "string"
-}

removedInput schema / properties / role

Removed value: -{
-  "description": "Share permission level.",
-  "enum": [
-    "admin",
-    "member",
-    "guest",
-    "view"
-  ],
-  "type": "string"
-}

Changed1 schema field changedAug 10, 2026

changedInput schema / properties / expires / description

Previous value: -"Expiration: workspace ISO 8601, share YYYY-MM-DD HH:MM:SS."New value: +"Membership expiration — `YYYY-MM-DD HH:MM:SS UTC` for BOTH workspace and share. ISO 8601 is NOT accepted (406)."

Changed1 schema field changedAug 6, 2026

changedInput schema / properties / display_limit / description

Previous value: -"How many members to return for the list action. Default 10, max 500. The MCP trims post-fetch; backend paging stays MCP-internal so the platform cache stays…"New value: +"How many members to return for the list action. Default 10, max 500. The MCP trims post-fetch; backend paging stays MCP-internal so the platform cache stays warm."

Changed5 schema fields changedJun 26, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "describe",
-  "add",
-  "remove",
-  "details",
-  "update",
-  "transfer-ownership",
-  "leave",
-  "join",
-  "join-invitation"
-]New value: +[
+  "describe",
+  "list",
+  "add",
+  "remove",
+  "details",
+  "update",
+  "transfer-ownership",
+  "leave",
+  "join",
+  "join-invitation"
+]

addedInput schema / properties / display_limit

Added value: +{
+  "description": "How many members to return for the list action. Default 10, max 500. The MCP trims post-fetch; backend paging stays MCP-internal so the platform cache stays…",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / entity_id / description

Previous value: -"Opaque ID of a specific object (file, comment, worklog entry, etc.). Pair with entity_type to disambiguate. 19-digit ID or custom name."New value: +"Workspace or share ID (19-digit numeric or custom name). Must match entity_type."

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum number of items to return (1-500, default 100)",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of items to skip (default 0)",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

Changed19 schema fields changedMay 5, 2026

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: -[
-  "add",
-  "remove",
-  "details",
-  "update",
-  "transfer-ownership",
-  "leave",
-  "join",
-  "join-invitation"
-]New value: +[
+  "describe",
+  "add",
+  "remove",
+  "details",
+  "update",
+  "transfer-ownership",
+  "leave",
+  "join",
+  "join-invitation"
+]

changedInput schema / properties / email_or_user_id / description

Previous value: -"Email address (to invite) or user profile ID (to add directly) (required for: add)"New value: +"Email (to invite) or user ID (to add directly)."

changedInput schema / properties / entity_id / description

Previous value: -"19-digit workspace or share ID, or custom name"New value: +"Opaque ID of a specific object (file, comment, worklog entry, etc.). Pair with entity_type to disambiguate. 19-digit ID or custom name."

changedInput schema / properties / entity_type / description

Previous value: -"Whether managing workspace or share membership"New value: +"Workspace or share."

changedInput schema / properties / expiration / description

Previous value: -"Membership expiration (alias for expires, share only) (used by: update)"New value: +"Alias for expires (share only)."

changedInput schema / properties / expires / description

Previous value: -"Membership expiration date (workspace: ISO 8601, share: YYYY-MM-DD HH:MM:SS) (used by: add, update)"New value: +"Expiration: workspace ISO 8601, share YYYY-MM-DD HH:MM:SS."

changedInput schema / properties / force_notification / description

Previous value: -"Force send notification email to existing user (workspace-only) (used by: add)"New value: +"Force notify existing user (workspace-only)."

changedInput schema / properties / invitation_action / description

Previous value: -"Whether to accept or decline the invitation (required for: join-invitation; optional for: join)"New value: +"Accept or decline."

changedInput schema / properties / invitation_expires / description

Previous value: -"Invitation expiration date (ISO 8601, workspace-only) (used by: add)"New value: +"Invitation expiration ISO 8601 (workspace-only)."

changedInput schema / properties / invitation_key / description

Previous value: -"Unique invitation key string (required for: join-invitation; optional for: join)"New value: +"Invitation key string."

changedInput schema / properties / member_id / description

Previous value: -"Member ID (required for: remove; required for workspace: details, update, transfer-ownership)"New value: +"Member ID (workspace)."

changedInput schema / properties / message / description

Previous value: -"Custom message to include in invitation email (10-255 chars) (used by: add)"New value: +"Invitation email message (10-255 chars)."

changedInput schema / properties / notifications / description

Previous value: -"Notification preference (workspace: string, share: enum format) (used by: add, update, join)"New value: +"Notification preference (workspace string)."

changedInput schema / properties / notify_options / description

Previous value: -"Notification preference for shares (alias for notifications) (used by: update, join)"New value: +"Notification preference (share)."

changedInput schema / properties / permissions / description

Previous value: -"Permission level for workspace members (admin, member, guest) (used by: add, update)"New value: +"Workspace permission level."

changedInput schema / properties / role / description

Previous value: -"Permission level for share members (admin, member, guest, view) (used by: add, update)"New value: +"Share permission level."

changedInput schema / properties / user_id / description

Previous value: -"User profile ID (required for share: details, update, transfer-ownership)"New value: +"User profile ID (share)."

changedInput schema / required

Previous value: -[
-  "action",
-  "entity_type",
-  "entity_id"
-]New value: +[
+  "action"
+]

First observedApr 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, so the safety profile is already structured. The description adds value by clarifying that it lists both active and pending members, which the annotations don't say. It could add more (pagination behavior, permissions), but it's 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?

Two sentences, zero waste, and the sibling routing is front-loaded. Every word earns its place.

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?

Complete for a read tool with full schema coverage and annotations covering safety. It clearly routes to the write counterpart. The only minor gap is not detailing return structure, but with no output schema and a list operation, that's acceptable and could be inferred.

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 does the heavy lifting. The description maps the two list modes ('active and pending', 'details') to the `action` enum values, which is useful but minimal. 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?

The description uses a specific verb ('read') on a specific resource ('workspace and share members') and explicitly distinguishes the read tool from its write sibling ('member_manage'). It also clarifies the sub-operations (list active and pending, details).

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?

It explicitly states when to use this tool versus the alternative: 'read' operations belong here, 'Writes are on member_manage'. This is the exact sibling routing pattern.

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?