Skip to main content
Glama

Fast.io

by io.fast.mcp
OverviewDiscussionsAdmin

invitation

Destructive

Workspace/share invitations: list, filter by state, update, revoke. Call action='describe' for the full action/param reference. Destructive: delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoInvitation state filter.
actionYesOperation. Use 'describe' for full action reference.
expiresNoUpdated expiration — `YYYY-MM-DD HH:MM:SS UTC`. ISO 8601 is NOT documented as accepted.
entity_idNoWorkspace or share ID (19-digit numeric or custom name). Must match entity_type.
new_stateNoNew invitation state.
entity_typeNoWorkspace or share.
permissionsNoUpdated permission level.
invitation_idNoInvitation opaque ID or invitee email.
notificationsNoNotification preference (workspace).
notify_optionsNoNotification preference (share).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / expires / description
      Previous value: -"Updated expiration (ISO 8601 or YYYY-MM-DD HH:MM:SS)."New value: +"Updated expiration — `YYYY-MM-DD HH:MM:SS UTC`. ISO 8601 is NOT documented as accepted."
  2. Changed1 schema field changed
    • 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."
  3. Changed12 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Operation: list (all), list-by-state (workspace only), update, delete"New value: +"Operation. Use 'describe' for full action reference."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "list-by-state",
-  "update",
-  "delete"
-]New value: +[
+  "describe",
+  "list",
+  "list-by-state",
+  "update",
+  "delete"
+]
    • 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 invitations"New value: +"Workspace or share."
    • changedInput schema / properties / expires / description
      Previous value: -"Updated membership expiration date (ISO 8601 or YYYY-MM-DD HH:MM:SS) (used by: update)"New value: +"Updated expiration (ISO 8601 or YYYY-MM-DD HH:MM:SS)."
    • changedInput schema / properties / invitation_id / description
      Previous value: -"Invitation opaque ID or invitee email (required for: update, delete)"New value: +"Invitation opaque ID or invitee email."
    • changedInput schema / properties / new_state / description
      Previous value: -"New invitation state (used by: update)"New value: +"New invitation state."
    • changedInput schema / properties / notifications / description
      Previous value: -"Updated notification preference (workspace only). For share, use 'notify_options'. (used by: update)"New value: +"Notification preference (workspace)."
    • changedInput schema / properties / notify_options / description
      Previous value: -"Updated notification preference (share only). For workspace, use 'notifications'. (used by: update)"New value: +"Notification preference (share)."
    • changedInput schema / properties / permissions / description
      Previous value: -"Updated permission level (workspace: admin/member/guest; share: admin/member/guest/view) (used by: update)"New value: +"Updated permission level."
    • changedInput schema / properties / state / description
      Previous value: -"Invitation state filter. Workspace supports all states; share supports pending/accepted/declined. (required for: list-by-state; optional for: list)"New value: +"Invitation state filter."
    • changedInput schema / required
      Previous value: -[
-  "action",
-  "entity_type",
-  "entity_id"
-]New value: +[
+  "action"
+]
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already indicate destructive behavior (destructiveHint=true), and the description reinforces this with 'Destructive: delete.' It adds context about update/revoke operations but does not detail side effects, permissions, or response behavior. The safety profile is mostly covered by annotations, with the description adding minimal extra value.

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 three short sentences that front-load the primary purpose, provide a clear directive for obtaining full details, and flag destructive actions. Every sentence serves a distinct and necessary role, with no redundancy or 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?

Given the tool's complexity (10 parameters, multiple actions) and absence of an output schema, the description provides a high-level overview and directs to action='describe' for complete details. It does not explicitly list all actions or parameter groups, but the describe reference compensates, making the description sufficiently complete for initial orientation.

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 all 10 parameters are already described in the schema. The description adds no additional parameter semantics beyond referencing action='describe' for full details. This matches the baseline for high schema coverage; no extra credit needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it manages 'Workspace/share invitations' with actions like list, filter, update, revoke, which distinguishes it from sibling tools like share or member. It could be more exhaustive by listing all actions (e.g., delete, describe), but the pointer to action='describe' compensates, making the purpose evident.

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

Usage Guidelines3/5

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

The description implies usage when managing workspace/share invitations, but it does not explicitly state when to use this tool versus alternatives or mention exclusions. The advice to call action='describe' for the full reference is helpful though limited. No direct comparison to sibling tools is given.

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