Skip to main content
Glama

akb_put_file

Upload a local file to a vault's S3-backed storage for PDFs, images, or datasets. Returns a URI for retrieval or deletion.

Instructions

Upload a local file to a vault's file storage (S3-backed). Use for PDFs, images, datasets, or any binary content too large for akb_put. Response includes the canonical uriakb://{vault}/coll/{collection}/file/{uuid} when stored under a collection, or akb://{vault}/file/{uuid} at the vault root — pass that to akb_get_file / akb_delete_file. MIME type is auto-detected from the filename extension unless overridden.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentNoParent location as a canonical URI — `akb://{vault}` for the vault root, `akb://{vault}/coll/{path}` for a collection. When given, the file is uploaded there and `vault`/`collection` are derived from the URI.
vaultNoVault name. Required unless `parent` is given.
file_pathYesAbsolute path to the local file to upload
collectionNoLogical grouping (like document collections). Ignored when `parent` is given.
descriptionNoBrief description of the file
mime_typeNoMIME type of the file (e.g. 'text/html', 'application/pdf', 'image/png'). Optional — if omitted, it is auto-detected from the filename extension. Override only when the extension is missing, ambiguous, or wrong.
Behavior3/5

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

Discloses S3 storage, MIME auto-detection, and URI format. Without annotations, it lacks details on file overwrite behavior, authentication needs, or size limits. Adequate but not comprehensive.

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, each serving a purpose: action+storage, URI usage, MIME handling. No fluff, efficient and front-loaded.

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?

Covers key aspects (type of content, URI, MIME) and references siblings. Missing details on error states, permissions, or idempotency, but sufficient for a file upload tool.

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?

Adds meaning beyond schema by explaining parent vs vault/collection derivation, MIME override conditions, and URI format. Schema coverage is 100% but description enriches context.

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?

The description clearly states the tool uploads a local file to a vault's S3-backed storage, specifies content types (PDFs, images, datasets) and distinguishes from akb_put for large binary content. It also explains the URI response and links to get/delete.

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 guidance on when to use (binary content too large for akb_put) and mentions MIME override contexts. However, doesn't explicitly list alternatives for non-file uploads or including when-not-to-use scenarios.

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/dnotitia/akb'

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