Skip to main content
Glama

Anima MCP Server

by io.github.AnimaApp
OverviewDiscussionsAdmin

Get ZIP Upload URL

artifact-get_zip_upload_url
Read-only

Step 1 of the zip import flow for artifact-create: for imports with binaries or over roughly 100 KB of source; small text-only projects pass files inline.

Flow:

  1. Call this tool: returns zipUploadId and presigned uploadUrl.

  2. HTTP PUT the project zip to uploadUrl.

  3. Call artifact-create (type import) with zipUploadId within 30 minutes of the last upload; the zip becomes the first commit and zipUploadId is single-use.

Rules: zip max 50MB; source, config, assets only — no node_modules or build output. Shell/executable files are skipped and reported. uploadUrl is a secret.

Presentations: purpose "presentation" reserves the upload for a presentation: PUT the presentation file itself (.key, .pptx, .odp or .pdf, max 256MB), then artifact-create with artifactType "presentation".

Returns: success, zipUploadId, uploadUrl, uploadUrlExpiresAt, nextSteps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
purposeNoReserve the upload for a specific artifact kind. Omit for app or markdown source. Pass "asset" to import images or video — an asset artifact can ONLY be created from an upload reserved this way, and an asset-reserved upload can only become an asset. Pass "presentation" to import a presentation: PUT the presentation file itself (.key, .pptx, .odp or .pdf, up to 256MB), not a zip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / purpose / description
      Previous value: -"Reserve the upload for a specific artifact kind. Omit for app or markdown source. Pass \"asset\" to import images or video — an asset artifact can ONLY be created from an upload reserved this way, and an asset-reserved upload can only become an asset."New value: +"Reserve the upload for a specific artifact kind. Omit for app or markdown source. Pass \"asset\" to import images or video — an asset artifact can ONLY be created from an upload reserved this way, and an asset-reserved upload can only become an asset. Pass \"presentation\" to import a presentation: PUT the presentation file itself (.key, .pptx, .odp or .pdf, up to 256MB), not a zip."
    • changedInput schema / properties / purpose / enum
      Previous value: -[
-  "asset"
-]New value: +[
+  "asset",
+  "presentation"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations with concrete operational facts: 30-minute expiry from last upload, single-use zipUploadId, 50MB zip cap, node_modules/build-output exclusions, executables skipped and reported, uploadUrl treated as a secret, and 256MB for presentations. None of this is derivable from the readOnly/openWorld annotations.

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?

Long but well-structured with bolded Flow / Rules / Presentations / Returns sections and the purpose front-loaded. Nearly every sentence carries a constraint (size limits, expiry, exclusions), though the Presentations block partially duplicates the schema description.

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?

For a multi-step upload flow with no output schema, the description covers the end-to-end sequence, time limits, size limits, content exclusions, the presentation variant, and explicitly enumerates the return fields. Nothing an agent needs to execute the flow correctly is missing.

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% and the single enum parameter is already fully documented in the schema, so the baseline is 3. The description's Presentations block mostly restates the schema's purpose description; it adds only the follow-up artifactType value, which is workflow rather than parameter meaning.

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?

The opening sentence states a specific verb and resource (get a ZIP upload URL) and positions it as 'Step 1 of the zip import flow for artifact-create', immediately walling it off from the other upload/creation siblings. Combined with the explicit inline-vs-upload threshold, an agent can tell what this tool is for without opening the schema.

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 when-to-use condition ('imports with binaries or over roughly 100 KB of source') and an explicit when-not ('small text-only projects pass files inline'), plus the precise follow-up sequence. It never mentions the sibling artifact-get_asset_upload_url, even though the schema's 'asset' purpose overlaps with that tool, leaving one routing decision to inference.

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

All Anima MCP Server toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources