Skip to main content
Glama

upload_image

Idempotent

Upload a JPEG, PNG or WebP image (5 MiB maximum). Returns an assetId for the document.

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": {
      "base64": "<base64>",
      "mime": "<mime>"
    },
    "name": "upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
mimeYes
base64Yes
idempotencyKeyNoOptional. Set a random key and reuse it exactly when retrying, so a retry is not applied twice

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"Unique random key for this operation; reuse exactly when retrying"New value: +"Optional. Set a random key and reuse it exactly when retrying, so a retry is not applied twice"
    • changedInput schema / required
      Previous value: -[
      -  "base64",
      -  "mime",
      -  "idempotencyKey"
      -]New value: +[
      +  "base64",
      +  "mime"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover mutability, idempotency and openness, so the bar is lower. The description still adds real value beyond them: the 5 MiB size ceiling and the fact that it returns an assetId, which is not derivable from structured fields. It omits retry/idempotency behavior, which the schema covers.

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?

Two short sentences, front-loaded with the action and constraints, then the return value. Nothing redundant or padded.

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

Completeness3/5

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

Adequate for a simple upload but leaves out how base64 content should be supplied and when the optional idempotency key matters — meaningful gaps given no output schema and the presence of a URL-based sibling.

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 only 33% (only idempotencyKey documented). The description restates the mime enum already present in the schema and adds an implicit size bound for the base64 payload, but never explains that base64 must be an encoded image string or mentions the idempotencyKey usage.

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 ... image') and names the accepted formats and return value. It does not differentiate from the sibling upload_image_from_url, so an agent must infer which to pick from the name alone.

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

Usage Guidelines2/5

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

No statement of when to use this versus upload_image_from_url (base64 payload vs URL source). The accepted-format list hints at the input shape but gives no selection guidance or preconditions.

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