Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Browse Tool

amount.browse

Lists remote subfolders on a mount to inspect folder contents or choose a destination; returns folder paths for deeper browsing.

Instructions

Read-only. List the remote sub-folders (at most 500, by name) of a folder on a mount, e.g. to answer "what is in my Google Drive folder X" or to pick a destination. Paths are relative to the mount as the manager sees it. Returns {path, folders:[{name, path}]}; pass a folder's path back as path to go deeper. Files are listed with amount.files (offloaded ones) or fetched with amount.fetch.

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

Input Schema

NameRequiredDescriptionDefault
pathNoRemote folder to list, e.g. "Pictures/Cats" (default: the top)
mountYesMount uuid from amount.mounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description must carry the behavioral load, and it does: read-only, a 500-item cap, folders-only results, and path relativity 'as the manager sees it.' It stops short of stating what happens on an invalid mount or path, or whether more than 500 entries can be paginated, which keeps it off a 5.

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?

Front-loads 'Read-only.' then the operation, then use cases, then the return contract and alternatives. Every clause carries information; nothing is restated from the schema or title.

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 two-parameter browse tool with no output schema, the description supplies the return shape ({path, folders:[{name, path}]}) and traversal mechanics, which is what an agent needs to call it. Only edge-case behavior (errors, truncation beyond 500) is absent.

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 would be 3, but the description adds real meaning: paths are relative to the mount as the manager sees it, the path defaults to the top, and a returned folder's `path` can be fed back into `path` to descend. That recursion contract is not in 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 ('List the remote sub-folders ... of a folder on a mount') with an explicit bound (at most 500, by name) that tells the agent this returns folders only, not files. It also differentiates itself from siblings by naming amount.files and amount.fetch for the file-listing and fetching cases.

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 concrete when-to-use scenarios ('what is in my Google Drive folder X' or 'to pick a destination') and routes the agent elsewhere for files. The alternative handling is explicit rather than inferred, so the agent can choose correctly without opening the sibling schemas.

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