Skip to main content
Glama

WELANDA Engraving Designer

Upload logo

upload_asset

Upload a logo/image (base64, PNG/JPEG/WebP/SVG, max 5 MB) for use in a design. Returns an assetId; reference it in an image object as { origin:"minio", bucket:"draft", key:"" }. Images are re-encoded to PNG server-side (metadata stripped). No URLs — base64 only.

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>",
      "dataBase64": "<dataBase64>"
    },
    "name": "upload_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesOriginal file name (label only; format is detected from bytes).
dataBase64YesBase64-encoded image bytes (PNG/JPEG/WebP/SVG). No URLs. Max 5 MB decoded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare write/non-idempotent/non-destructive, so the description carries real weight and does: it discloses server-side re-encoding to PNG with metadata stripped (a lossy transformation the caller would otherwise not know), the decoded size limit, and the assetId return plus the exact reference syntax. The non-idempotent hint is implicitly supported by the fact that each call mints a new assetId.

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?

The purpose and formats are front-loaded in the first clause, and every subsequent sentence adds a constraint (size, PNG conversion, reference syntax, no URLs). It is dense with nested parentheses though, which packs four separate facts into one opening sentence and slightly burdens scanning.

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

Completeness5/5

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

With only two required parameters, no output schema, and no nested objects, the definition covers everything an agent needs: accepted formats, size ceiling, the rejected input style (URLs), the server-side transformation, and how to consume the returned assetId. Nothing material is left to inference.

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%, and the description largely restates what the schema already says (base64-only, PNG/JPEG/WebP/SVG, 5 MB decoded, filename as label). It adds no new syntax, encoding, or validation nuance for either parameter, so the baseline of 3 applies.

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?

"Upload a logo/image ... for use in a design" gives a specific verb plus resource and scope, and the parenthetical pins accepted formats and the 5 MB ceiling. The statement that it returns an assetId referenced as { origin:"minio", bucket:"draft", key:"<assetId>" } makes the tool's role in the workflow unmistakable, and no sibling (create_design, render_preview, etc.) could be confused with it.

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?

It establishes the context of use (embedding an image in a design) and explicitly rules out a common wrong path with "No URLs — base64 only." What it lacks is any pointer to a sibling alternative or a statement of preconditions, but no other listed tool performs uploads, so the practical gap is small.

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