Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Mounts Tool

amount.mounts

List storage mounts (Google Drive, Dropbox, S3) available to the acting manager with name, driver, scope and health, or resolve a single mount by name. Never returns credentials.

Instructions

Read-only. List the storage mounts (Google Drive, Dropbox, S3, ...) the acting manager may use: uuid, name, driver, scope (personal/site/config) and health status. Never returns credentials. With name (e.g. "my google drive") it resolves one mount; if several match the call fails with candidates=[{uuid,name,...}] - ask the person which one, then use that uuid in later calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "amount.mounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional mount name or kind, e.g. "google drive" or "S3 backups"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations are empty, so the description carries the full burden and does: it declares read-only behavior, a security guarantee ("Never returns credentials"), and the exact failure mode with the `candidates=[{uuid,name,...}]` payload. That error-shape disclosure is the kind of behavior an agent cannot get 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.

Conciseness5/5

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

Three sentences, front-loaded with the read-only guarantee and the resource, then the return fields, then the edge-case workflow. No filler or repeated information; the longest sentence is long because it carries the ambiguity protocol.

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?

There is no output schema and no annotations, yet the description covers return fields, the no-credentials guarantee, single-parameter resolution semantics, and the multi-match error contract with follow-up instructions. Nothing an agent needs to call this correctly 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 goes beyond it by explaining what `name` actually does semantically (resolves one mount, accepts kind-like values such as "my google drive") and what happens when several match. It adds real meaning rather than restating the parameter.

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 ("List the storage mounts") plus the exact scope (mounts the acting manager may use) and enumerates the returned fields: uuid, name, driver, scope, health status. An agent knows immediately what it gets back and can distinguish this from browse/files/computers style siblings.

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 explicit conditional usage for the one parameter: without `name` it lists, with `name` it resolves a single mount, and on ambiguity it prescribes the recovery path (ask the person, then reuse the uuid in later calls). It stops short of naming a sibling alternative or stating when-not-to-use, which keeps it off a 5.

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