Skip to main content
Glama

Typebar (formerly SuperDocs)

upload_template_base64

Templates persist across sessions and can be referenced by the AI when drafting new documents (e.g., "draft an NDA using my standard template"). Stored at user or organization scope. Ideal for boilerplate, branded letterheads, recurring document structures, or compliance-required templates. Supports the same formats as document upload: .docx, .pdf, .txt, .rtf, .md, .html, .htm, .tex. Max 50 MB validated; note the hosted transport layer caps any REQUEST BODY at ~32 MB and rejects larger ones at the gateway with an HTML (not JSON) error — base64 inflates content ~33%, so inline uploads are reliable up to ~20 MB of file bytes; beyond that use request_upload_url (pre-signed flow, up to 100 MB).

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>",
      "file_base64": "<file_base64>"
    },
    "name": "upload_template_base64"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesOriginal filename with extension (e.g. 'contract.pdf'). Used for file type detection.
session_idNoSession ID. Auto-generated if not provided.
file_base64YesBase64-encoded file content.
return_htmlNoWith a session_id: false (default) returns compact metadata only (chunks_count, version_id, page_setup) — the document is loaded into the session and you edit it via chat, keeping your context small; true returns the full parsed HTML inline. Ignored on the convert-only path (no session_id), which always returns the converted html.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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: persistence across sessions, user/org scope, supported formats, 50 MB validation, ~32 MB gateway cap, base64 inflation, and the ~20 MB reliable inline threshold. It omits auth/permission requirements, duplicate/overwrite behavior, and success/return semantics, so it is strong but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is useful but not front-loaded: it opens with persistence and use cases rather than the upload action. The size-limit discussion is necessary, but the illustrative NDA example and some repetition make it longer than needed.

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?

For a no-annotation, no-output-schema upload tool, the description covers formats, size limits, persistence, and the large-file alternative well. It still leaves gaps around scope selection (user vs organization), overwrite/duplicate handling, and what a successful call returns, so an agent lacks some operational context.

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. The description adds meaningful parameter context beyond the schema by explaining the transport body cap, base64 inflation, and when to switch to request_upload_url for file_base64; it does not add much for filename, session_id, or return_html.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains template persistence, scope, and use cases, but never states the action directly (e.g., 'uploads a base64-encoded template file'). The resource is clear, but the verb is only implied by 'inline uploads' and the tool name, so it falls short of a specific verb+resource statement.

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 concrete when-to-use examples (boilerplate, letterheads, recurring structures, compliance templates) and names request_upload_url as the alternative for files beyond ~20 MB. It does not explicitly contrast with upload_document_base64 or upload_attachment_base64, so sibling selection is only partly covered.

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.