Fast.io

User Management

user_manage

Destructive

Fastio user account (write): profile, invitations, assets, report-bug. Destructive: close, asset-delete, invitation-decline. Reads are on user.

Input Schema

TableJSON Schema

Name	Required	Description
`blob`	No	Plain-text excerpt (error body, short log), max 32 KB. No secrets or file content.
`title`	No	Bug report title, 1-200 chars.
`action`	Yes	Operation; 'describe' lists the actions.
`content`	No	Plain-text asset content.
`user_id`	No	19-digit user ID or email.
`category`	No	Bug report area.
`endpoint`	No	Failing call as 'METHOD /path', no host or query.
`filename`	No	Original filename.
`last_name`	No	Family name.
`asset_name`	No	Asset type name (e.g. profile_pic).
`error_code`	No	Error code of the failed call.
`first_name`	No	Given name.
`request_id`	No	From the failed tool result.
`description`	No	Bug report body: steps, expected vs actual. Max 8 KB. No secrets.
`http_status`	No	HTTP status of the failed call.
`occurred_at`	No	Failure time, 'YYYY-MM-DD HH:MM:SS UTC', last 30 days.
`confirmation`	No	Account email or user ID.
`content_type`	No	MIME type.
`invitation_id`	No	Invitation opaque ID or key.
`content_base64`	No	Base64 binary content.
`invitation_key`	No	Invitation key.
`describe_action`	No	With action='describe': return one action's params and notes instead of the action index.
`idempotency_key`	No	16-64 chars [A-Za-z0-9_-]; generated when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026
- removedInput schema / properties / email_address
```
Removed value: -{
-  "description": "Email address.",
-  "type": "string"
-}
```

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "describe",
-  "update",
-  "close",
-  "accept-all-invitations",
-  "asset-upload",
-  "asset-delete",
-  "report-bug"
-]New value: +[
+  "describe",
+  "update",
+  "close",
+  "accept-all-invitations",
+  "invitation-accept",
+  "invitation-decline",
+  "asset-upload",
+  "asset-delete",
+  "report-bug"
+]

addedInput schema / properties / invitation_id

Added value: +{
+  "description": "Invitation opaque ID or key.",
+  "type": "string"
+}

AddedOct 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the specific destructive action set, which is useful beyond the generic annotation. It does not explain permissions, reversibility, or confirmation requirements.

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?

Three compact fragments, front-loaded with scope, then destructive actions, then the read alternative. Every clause carries routing or safety value and there is no padding.

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 23-parameter multi-action tool, the description supplies essential write-vs-read routing and destructive-action categorization. The fully described schema and safety annotations cover most remaining gaps, though the description omits confirmation/idempotency nuances and per-action return expectations.

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 coverage is 100%, so all 23 parameters are documented in the input schema. The description adds grouping for the `action` enum and identifies destructive action values, but does not clarify conditional requirements such as when `confirmation` is needed or how the other parameters interact per action.

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 the resource (Fastio user account) and operation type (write), enumerates action groups (profile, invitations, assets, report-bug) and destructive actions. Explicitly distinguishes this tool from the read-only `user` sibling.

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?

Directs all read operations to the `user` sibling, which clearly scopes this tool to writes. It also flags destructive actions (close, asset-delete, invitation-decline) so the agent can route and call them cautiously.

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?