Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Deliver Tool

amount.deliver

Sends site files or folders to a storage mount for backup or transfer; runs in background and returns a run UUID to poll for completion.

Instructions

Send a file or a whole folder from the site to a storage mount (back up / put on Google Drive, or onto one of the person's own computers - see amount.computers; a computer's name such as "mypc" works as mount, with folder = "/"). When a name is taken at the other end, a newer file replaces an older one only if destructive tools are allowed for this call, otherwise it is kept and the result says so. Runs in the background and returns at once with a run uuid: poll amount.status with it until finished is true. The manager must be able to see the path in the file manager, otherwise the call is refused. If mount is omitted or unclear the call fails with candidates=[{uuid,name,...}]: ask the person which one, then call again with that uuid. With move=true the local copy is deleted after a verified upload (destructive; only when asked).

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": {
      "path": "<path>"
    },
    "name": "amount.deliver"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveNoDelete the local file after a verified upload. Default false.
pathYesSite-relative file or folder, e.g. "assets/images/cat.png" or "assets/backup"
siteNoThe site the person named ("site.com"): refused if this installation does not serve it.
mountNoMount uuid (preferred) or a name such as "google drive"
folderNoRemote folder to put it in, e.g. "Pictures/Cats" (default: the top)
publicNoKeep the file publicly reachable at its site URL. Default false (private).
on_conflictNo"skip" keeps a file already there; "newer" lets a newer file replace an older one (needs destructive permission). Default: newer when destructive tools are allowed, else skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare only readOnlyHint=false, so the description carries the burden and does it well: asynchronous background execution with a run uuid, overwrite behavior gated on destructive permission, refusal when the path isn't visible in the file manager, structured candidate-list failure, and local-copy deletion with move=true. These are behavioral facts the agent could not derive from the schema or 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?

Purpose and destination options are front-loaded in the first sentence, and every later clause adds a rule the agent needs. It is a single dense block, though, and the on_conflict default is restated from the schema, so it could be tightened or split into a short behavior section.

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 seven-parameter, asynchronous mutation tool with no output schema, the description covers the return contract (run uuid, poll via amount.status), the failure contract (candidate list), and the destructive-operation precondition. Nothing an agent needs in order to invoke or recover from this call is missing.

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, and the description adds real meaning on top: `mount` accepts a computer name like "mypc" as well as a uuid, `folder` is interpreted relative to that shared folder, and `move`/`on_conflict` are tied to destructive permission. It doesn't explain `public` or the `site` refusal condition in the prose, leaving those to the schema.

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 and resource ("send a file or a whole folder from the site to a storage mount") and enumerates the destination classes (backup, Google Drive, the person's own computer) rather than restating the title. It also distinguishes itself from siblings by name, pointing to amount.computers for computer mounts and amount.status for polling.

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

Usage Guidelines5/5

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

Gives explicit operating instructions: poll amount.status with the run uuid until `finished`, re-call with a candidate uuid when `mount` is ambiguous, ask the person before using move=true. It also states the precondition (manager must see the path) and the failure mode when it isn't met.

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