Skip to main content
Glama

Fast.io

by io.fast.mcp
OverviewDiscussionsAdmin

asset

Destructive

Brand asset management (logos, banners, profile photos) on org/workspace/share/user. Upload, delete, list, read. Call action='describe' for the full action/param reference. Destructive: delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation. Use 'describe' for full action reference.
contentNoPlain text content (e.g. SVG).
asset_idNoAsset ID or name.
metadataNoAdditional metadata as JSON array string.
entity_idNoOpaque ID of a specific object (file, comment, etc.). Pair with entity_type to disambiguate. Entity ID (optional for user).
file_nameNoOriginal file name.
asset_typeNoAsset type key (e.g. 'logo', 'banner', 'photo').
entity_typeNoEntity type.
file_base64NoBase64-encoded binary content.
content_typeNoMIME type (default application/octet-stream).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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. Entity ID (optional for user)."New value: +"Opaque ID of a specific object (file, comment, etc.). Pair with entity_type to disambiguate. Entity ID (optional for user)."
  2. Changed12 schema fields changed
    • 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: -[
-  "upload",
-  "delete",
-  "types",
-  "list",
-  "read"
-]New value: +[
+  "describe",
+  "upload",
+  "delete",
+  "types",
+  "list",
+  "read"
+]
    • changedInput schema / properties / asset_id / description
      Previous value: -"Asset ID or name (required for: upload, delete, read if asset_type not provided)"New value: +"Asset ID or name."
    • changedInput schema / properties / asset_type / description
      Previous value: -"Asset type key (e.g. 'logo', 'banner', 'photo') (required for: upload, delete, read if asset_id not provided)"New value: +"Asset type key (e.g. 'logo', 'banner', 'photo')."
    • changedInput schema / properties / content / description
      Previous value: -"Plain text content (e.g. SVG). Use this instead of file_base64 for text-based assets. (used by: upload)"New value: +"Plain text content (e.g. SVG)."
    • changedInput schema / properties / content_type / description
      Previous value: -"MIME type (e.g. image/png). Defaults to application/octet-stream (used by: upload)"New value: +"MIME type (default application/octet-stream)."
    • changedInput schema / properties / entity_id / description
      Previous value: -"Entity ID (not needed for 'types' action or 'user' entity_type when operating on authenticated user) (required for: list, upload, delete, read for non-user entities)"New value: +"Opaque ID of a specific object (file, comment, worklog entry, etc.). Pair with entity_type to disambiguate. Entity ID (optional for user)."
    • changedInput schema / properties / entity_type / description
      Previous value: -"Entity type the asset belongs to"New value: +"Entity type."
    • changedInput schema / properties / file_base64 / description
      Previous value: -"Base64-encoded file content for binary files. Use content for text. (used by: upload)"New value: +"Base64-encoded binary content."
    • changedInput schema / properties / file_name / description
      Previous value: -"Original file name (e.g. logo.png) (used by: upload)"New value: +"Original file name."
    • changedInput schema / properties / metadata / description
      Previous value: -"Additional metadata as JSON array string (used by: upload)"New value: +"Additional metadata as JSON array string."
    • changedInput schema / required
      Previous value: -[
-  "action",
-  "entity_type"
-]New value: +[
+  "action"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations include destructiveHint=true, and the description explicitly calls out 'Destructive: delete', adding specificity beyond the annotation. It also discloses the range of actions. No contradiction with annotations (readOnlyHint=false, destructiveHint=true).

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 sentences, front-loaded with purpose, followed by operational scope and a clear pointer to the describe action. Every sentence earns its place with no redundancy.

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?

The tool has 10 parameters and no output schema, but the schema itself is richly described. The description covers the main actions and explicitly defers to action='describe' for full details. Minor gap: the 'types' action is not mentioned, but the pointer to describe mitigates this.

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?

The input schema has 100% description coverage, so all parameters are already documented in the schema. The tool description does not add parameter-level meaning beyond the schema, but it does provide domain context (e.g., logos, banners, profile photos). 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?

Description states a specific verb+resource: 'Brand asset management' with concrete asset types (logos, banners, profile photos) and scope (org/workspace/share/user). It lists key operations (upload, delete, list, read) and distinguishes itself from generic sibling tools like upload/download by naming the asset domain.

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?

Provides clear context on what the tool manages and its entity scope. Points users to action='describe' for the full action/param reference, which is useful meta-guidance. However, it does not explicitly state when to use this tool over alternatives or when not to use it.

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