Skip to main content
Glama
prismeai

Prisme.ai MCP Plugin

Official
by prismeai

upload_file

Upload files to a Prisme.ai workspace via local path, remote URL, or data URI. Returns file details including URL, ID, and MIME type.

Instructions

Upload a file to the Prisme.ai workspace's file storage. Returns the uploaded File object(s) with url, id, name, mimetype, size. The file source can be provided in one of three ways: path (local filesystem), url (remote URL fetched by the MCP), or dataUri (data:mime;base64,... string). Exactly one of these must be set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoRemote URL to fetch and re-upload to Prisme. Mutually exclusive with `path` and `dataUri`.
pathNoLocal filesystem path to the file to upload. Mutually exclusive with `url` and `dataUri`.
publicNoSet to true to grant public-read ACL. Default is true on the API side.
dataUriNoData URI string (e.g. `data:image/png;base64,iVBORw0...`). Mutually exclusive with `path` and `url`.
fileNameNoOverride the file name stored on Prisme. Defaults to the basename of `path`/`url`, or `upload` for dataUri.
metadataNoArbitrary metadata to attach to the file.
shareTokenNoIf true, the response includes a `shareToken` that can be appended as `?token=...` to bypass auth.
contentTypeNoOverride the MIME type. Defaults to value detected from extension/dataUri, or `application/octet-stream`.
environmentNoOptional environment name (from PRISME_ENVIRONMENTS) to use specific API URL and workspace
workspaceIdNoAlternative: direct workspace ID (use workspaceName instead when possible)
expiresAfterNoBest-effort expiration delay in seconds. The file will be deleted on the next API restart after this delay.
workspaceNameYesWorkspace name that resolves to ID via PRISME_WORKSPACES or PRISME_ENVIRONMENTS mapping
Behavior3/5

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

No annotations provided, so description covers return fields, source fetching behavior, defaults (public, fileName), and best-effort expiration, but lacks details on authentication needs, error handling, file size limits, or what happens if file already exists.

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?

Single paragraph, front-loaded with main purpose and return fields, then explains source options efficiently with no wasted words.

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?

No output schema, so description compensates by listing return fields and explaining source methods. Covers optional parameters but misses constraints like file size limits or error scenarios; mostly complete.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds value by clarifying mutual exclusivity of source parameters, default fileName logic, and workspace resolution, which goes beyond schema descriptions.

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 clearly states 'Upload a file to the Prisme.ai workspace's file storage' and lists return fields, distinguishing it from sibling tools like delete_file, get_file, and list_files.

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?

Describes the three mutually exclusive source options (path, url, dataUri) and exactly one must be set, but does not explicitly state when not to use this tool or compare to siblings for file operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prismeai/prismeai-mcp-debug'

If you have feedback or need assistance with the MCP directory API, please join our Discord server