Fast.io

event

Idempotent

Event log and activity monitoring for workspaces and shares. Also surfaces the per-member DASHBOARD — a 'what's on your plate' feed of cards (@mentions, file activity) for one workspace, with view-only dismiss/snooze and a best-effort AI overlay. Call action='describe' for the full action/param reference. Verbosity (detail param): search/activity-list/activity-poll default to terse (compact rows). summarize defaults to standard (envelope around the AI summary). details defaults to full (drill-down). Pass an explicit detail='terse'|'standard'|'full' to override (best-effort on summarize/activity-list/activity-poll — only search/details honor output=; see describe).

Input Schema

TableJSON Schema

Name	Required	Description
`wait`	No	Max seconds server holds connection (1-95, default 95).
`event`	No	Exact event name. See describe action for catalog.
`limit`	No	Max results (1-250, default 100).
`action`	Yes	Operation. Use 'describe' for full action reference.
`cursor`	No	Last activity timestamp for incremental polling.
`detail`	No	Per-record verbosity for search/summarize/details/activity-list/activity-poll. Defaults: terse for search/activity-list/activity-poll (compact rows), standard for summarize, full for details (drill-down). See action='describe' for per-level field lists.
`offset`	No	Pagination offset.
`org_id`	No	Filter by organization profile ID.
`user_id`	No	Filter by the event's stored subject column. DO NOT read it as "the person this event is about": the platform DERIVES that column instead of taking it from the emitter, so it can name an arbitrary related user rather than the subject. For "what did this person do", use calling_user_id (the actor) and read its note. See the search note before relying on either.
`card_key`	No	Dashboard card identity "<lane>:<id>" (e.g. "mention:123"). From a dashboard-list card. Required for dashboard-dismiss/dashboard-undismiss; URL-encoded into the path by the server.
`category`	No	Event category. See describe action for valid values. `node` IS THE AI/RAG PIPELINE, NOT FILE OPERATIONS — file activity lives under `workspace` AND `share`, so query both. CLOUD IMPORT IS NOT `cloudsync` HERE — that is an ACTIVITY field on a different taxonomy and returns nothing rather than erroring. Use category="import", narrowed with subcategory="cloud_import" for graft traffic only.
`event_id`	No	Alphanumeric event opaque ID.
`share_id`	No	Filter by share profile ID.
`entity_id`	No	Opaque ID of a specific object (file, comment, etc.). Pair with entity_type to disambiguate. 19-digit workspace, share, or File Share ID to monitor (activity-poll long-polls GET /activity/poll/{id}/ — for a File Share id this surfaces its file_share_* feed to WORKSPACE MEMBERS only; recipients get no feed).
`object_id`	No	Filter by related object opaque ID (file, folder, etc.).
`context_id`	No	Alias for profile_id (either name works)
`profile_id`	No	Polymorphic context ID. Pair with profile_type=workspace\|share\|org\|fileshare. Use workspace_id instead when only workspaces are valid. 19-digit profile ID (workspace, share, or File Share).
`visibility`	No	Filter by event visibility level (external_audit_log \| external). Default returns both, excludes internal.
`created_max`	No	ISO 8601 datetime — events on or before.
`created_min`	No	ISO 8601 datetime — events on or after.
`subcategory`	No	Event subcategory. See describe action for valid values.
`acknowledged`	No	Filter by acknowledgment status.
`context_type`	No	Alias for profile_type (either name works).
`lastactivity`	No	Timestamp from prior poll's response. Omit on first call.
`profile_type`	No	Profile type: "workspace", "share", or "fileshare". `fileshare` is valid for activity-list (long-poll a File Share's feed — workspace members only; recipients get no feed).
`snooze_until`	No	Optional for dashboard-dismiss: a future "Y-m-d H:i:s UTC" timestamp to snooze the card until (it reappears after). Omit for a permanent dismiss.
`user_context`	No	Focus guidance for AI summary, e.g. "Focus on uploads".
`workspace_id`	No	Workspace opaque ID. Use this when only workspaces are valid (not shares or other contexts). For polymorphic contexts use profile_id. Filter by workspace profile ID.
`calling_user_id`	No	Filter by the user who triggered the event.
`parent_event_id`	No	Filter by parent event ID for serial/batch events. SCOPE-EXCLUSIVE: cannot combine with any filter other than acknowledged, limit, offset.

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behaviors: DASHBOARD dismiss/snooze is view-only, the AI overlay is best-effort, activity-poll long-polls with server-held connections, File Share feeds are visible to workspace members only, and incorrect category choices like 'cloudsync' return nothing rather than erroring. This is substantial, decision-critical transparency.

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?

The description is dense and front-loaded with purpose, then moves into actionable defaults and exceptions. It is slightly run-on in the verbosity section, but every sentence carries useful information, especially for a 30-parameter umbrella tool.

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, multi-action tool with no output schema, the description covers major caveats, defaults, and points to action='describe' for the full action/param reference. It does not spell out return shapes beyond compact rows/envelope/drill-down hints, but the schema plus describe action make the definition reasonably complete.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds high-value semantics beyond the schema: user_id is not the actor, category 'node' means AI/RAG pipeline rather than file operations, cloud import is not 'cloudsync', and only search/details honor output=. These nuances prevent real invocation errors that the schema alone would not catch.

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 the tool's resource: event log and activity monitoring for workspaces and shares, plus the per-member DASHBOARD feed. It has a specific scope, though it does not explicitly differentiate itself from sibling tools by name.

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?

The description gives actionable usage guidance: call action='describe' for the full reference, and it explains verbosity defaults and which actions honor which parameters. It lacks explicit exclusion statements for sibling tools, but the context is clear enough for an agent to know when event activity/dashboard functionality is needed.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool covers a clearly distinct domain (auth, storage, shares, comments, events, AI, etc.), and overlapping concepts like share vs. fileshare are explicitly disambiguated with deprecation notes and cross-references. An agent can reliably select the correct tool for a task without ambiguity.

Naming Consistency3/5

Tool names are all lowercase single words, but they mix nouns (user, org, workspace) with verbs (download, find, upload) and include a hyphenated 'how-to'. There is no consistent verb_noun or noun-only pattern, though the names are still readable and memorable.

Tool Count4/5

19 tools is slightly above the typical 3-15 sweet spot, but the platform's breadth (auth, file management, sharing, collaboration, AI, metadata, and help) justifies this count. Each tool represents a substantial domain area, so none feel redundant.

Completeness5/5

The toolset provides full lifecycle coverage for the platform: authentication, user/org/workspace management, file storage/upload/download/search, sharing (both quickshare and durable file shares), comments, events, metadata pipelines, AI assistance, and product help. No obvious dead ends or missing operations are apparent.

Resources

Need Help?