Skip to main content
Glama

Typebar (formerly SuperDocs)

upload_image_base64

Upload an image (base64-encoded) and get a stable URL to reference in a document via .

Accepts PNG/JPEG/WebP/GIF/SVG, up to 10 MB decoded. Send raw base64 or a data: URL in image_base64. This is the agent-friendly counterpart to the browser multipart upload — use it to save a generated or fetched image so a document can embed it.

Embed the returned url (the stable canonical reference — it never expires and every document read serves it as a fresh time-limited signed link). view_url is such a signed link for immediately viewing/downloading the image outside a document; it expires, so never embed it.

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": {
      "image_base64": "<image_base64>"
    },
    "name": "upload_image_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNoOptional original filename (used only to infer content type).
content_typeNoOptional MIME type, e.g. image/png. Defaults to image/png.
image_base64YesThe image bytes, base64-encoded (raw base64 or a data: URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses important behavior: accepted formats, 10 MB decoded limit, raw base64 or data URL input, stable canonical URL, and expiring signed view_url. It does not cover authentication, overwrite behavior, or error cases, but the core upload and return semantics are well explained.

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?

The description is front-loaded with the core action and return value, then adds format/size constraints, usage guidance, and URL semantics. Every sentence contributes useful information without repetition.

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?

There is no output schema, so the description appropriately explains the returned url and view_url, including expiration behavior. It is complete enough to call the tool correctly, though it omits auth requirements and failure behavior.

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%, so the baseline is 3, but the description adds meaningful constraints beyond the schema: accepted image formats, the 10 MB decoded size limit, and that image_base64 may be raw base64 or a data URL. It does not add detail for filename or content_type beyond what the schema already provides.

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?

The description states a specific verb and resource: upload a base64-encoded image and get a stable URL for embedding in a document. It clearly distinguishes the image use case from browser multipart upload, but it does not explicitly name or differentiate itself from sibling tools such as upload_attachment_base64 or upload_document_base64.

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 gives a clear use case: save a generated or fetched image so a document can embed it. It also warns to embed the stable url and never the expiring view_url. It does not state when to prefer a sibling upload tool or when not to use this one.

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.