Skip to main content
Glama

Upload to storage

storage_upload
Idempotent

Upload a base64 object to app storage

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filename": "<filename>",
      "data_base64": "<data_base64>"
    },
    "name": "storage_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
project_idNoProject id (or use session from use_project)
data_base64Yes
content_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world write, so the safety profile is covered. The description adds only that the payload must be base64. It says nothing about overwrite semantics (implied by idempotentHint but not explained), size caps, auth/project scoping, or what a successful upload returns.

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?

A single front-loaded sentence with no filler. It is efficient, but the terseness is under-specification rather than disciplined brevity, so it does not reach 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with 25% schema coverage and no output schema, the definition is far too thin. It omits filename/content_type semantics, overwrite behavior, and what the tool returns (URL, key, metadata), all of which an agent needs to call it correctly.

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

Parameters2/5

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

Schema coverage is only 25%: just project_id is documented. The description gives meaning for data_base64 (must be base64-encoded) but leaves filename (path? key? overwrites existing object?) and content_type (defaults, accepted values) entirely unexplained in both schema and description.

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?

States a specific verb and resource: upload a base64-encoded object into app storage. The mention of 'base64' is the one detail that hints at how this differs from the sibling upload_file, though it never says so explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the base64 requirement; an agent can infer this is for inline-encoded payloads rather than file paths, but the description never names upload_file as the alternative or states when to pick each. No prerequisites, size limits, or overwrite conditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources