Skip to main content
Glama
Sign In

Autario

by com.autario
OverviewDiscussionsAdmin

upload_app_bundle

Idempotent

Upload or replace the code of an app YOU own: one entry document (content: HTML or JavaScript, max 512 KB), or a bundle of files (files: index.html plus the JavaScript, CSS, images, fonts and further HTML pages it loads by relative path, max 50 files, 1 MB each, 2 MB in total; images and fonts base64). A new upload replaces the whole bundle of that version. autario stores it and serves it inside a locked sandbox with no outbound network access, so the app reads World Bank, FRED, Eurostat, SEC and connector data through autario.js (autario.query, autario.datasets, autario.artifacts) rather than calling anything itself; autario inlines the SDK into the served page, so a script tag for https://autario.com/autario.js is optional. Re-uploading the same version replaces it in place. Use it to ship a new build of an app you created with create_app, or to fix one after a user reports something.

Input Schema

NameRequiredDescriptionDefault
filesNoA multi-file app: index.html plus every file it loads by relative path (e.g. "app.js", "css/style.css", "img/logo.png", "about.html"). Paths are relative, use "/", no "..". Allowed: html, js, mjs, css, json, svg, png, jpg, webp, woff2. Max 50 files, 1 MB each, 2 MB in total. Put index.html in this list or pass it as content. Links between the HTML pages work, every page gets autario.js.
app_idYesId of an app you own, as returned by create_app. An app you do not own answers not found.
contentNoThe entry document itself (one HTML file), or index.html when you also send files. Give content, files, or both.
versionNoOptional version label this bundle belongs to.
content_typeNoType of content when it is the only file. Default text/html.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"The entry document itself."New value: +"The entry document itself (one HTML file), or index.html when you also send files. Give content, files, or both."
    • changedInput schema / properties / content_type / description
      Previous value: -"Default text/html."New value: +"Type of content when it is the only file. Default text/html."
    • addedInput schema / properties / files
      Added value: +{
+  "description": "A multi-file app: index.html plus every file it loads by relative path (e.g. \"app.js\", \"css/style.css\", \"img/logo.png\", \"about.html\"). Paths are relative, use \"/\", no \"..\". Allowed: html, js, mjs, css, json, svg, png, jpg, webp, woff2. Max 50 files, 1 MB each, 2 MB in total. Put index.html in this list or pass it as content. Links between the HTML pages work, every page gets autario.js.",
+  "items": {
+    "properties": {
+      "content": {
+        "description": "The file: text as is, binary (images, fonts) as base64 with encoding \"base64\".",
+        "type": "string"
+      },
+      "encoding": {
+        "description": "Default utf8.",
+        "enum": [
+          "utf8",
+          "base64"
+        ],
+        "type": "string"
+      },
+      "path": {
+        "description": "Relative path inside the app, e.g. \"js/app.js\".",
+        "type": "string"
+      }
+    },
+    "required": [
+      "path",
+      "content"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "app_id",
-  "content"
-]New value: +[
+  "app_id"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / app_id / description
      Previous value: -"The app id."New value: +"Id of an app you own, as returned by create_app. An app you do not own answers not found."
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive, closed-world), yet the description adds substantial non-obvious behavior: a new upload replaces the entire bundle of that version, re-uploading the same version replaces in place, the code runs in a locked sandbox with no outbound network access, and the SDK is inlined so the script tag is optional. These are the exact traits an agent cannot derive from structured fields.

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?

Front-loaded with the verb, resource and the two payload modes, then the replace semantics and sandbox behavior. It is dense but every clause is load-bearing; the autario.js detail is arguably context rather than invocation guidance, which slightly blurs the focus.

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?

For a complex 5-parameter mutation tool with no output schema, the description covers payload rules, replacement semantics, ownership errors and runtime environment thoroughly. It does not say what the call returns (e.g. a version or preview URL, which a sibling get_app_preview_url implies exists), leaving a small gap since no output schema exists to fill it.

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 description coverage is 100%, so the schema already documents app_id, files, content, version, content_type and the encoding enum. The description largely restates the same constraints (file counts, size caps, base64 for binary, content-as-index.html), so it adds little beyond the baseline when the schema does the heavy lifting.

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?

States a specific verb+resource ('Upload or replace the code of an app YOU own') and immediately distinguishes the two accepted payload shapes (single entry document vs multi-file bundle). It also separates this tool from create_app, which it names as the origin of the app being shipped.

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?

Gives clear when-to-use context: 'ship a new build of an app you created with create_app, or to fix one after a user reports something,' and states the ownership precondition (an app you do not own answers not found). It does not explicitly contrast against nearby siblings such as update_app_manifest or write_app_artifact, so an agent must infer the boundary.

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

All Autario toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources