Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Rules Tool

amount.rules

Retrieves read-only standing folder rules from aMount, including mount targets, schedules, copy or move modes, visibility, offloaded totals, and last run details for referencing rule UUIDs.

Instructions

Read-only. The standing folder rules (site folder -> mount, schedule, mode copy/move, visibility, offloaded totals, last run) the manager owns. Rules are created in the aMount page; one-off deliveries from amount.deliver are not listed. Use a rule uuid with amount.files, amount.runs and amount.measure.

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.rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations are empty, so the description carries the burden; it does declare 'Read-only' and clarifies the provenance of the data (manager-owned rules, created in the aMount page, excluding one-off deliveries). It says nothing about volume, pagination, ordering, or whether all folders' rules are returned, which are relevant for a zero-parameter list operation.

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?

Three sentences, front-loaded with the read-only constraint and the core resource. The parenthetical field list is dense but purposeful; the only mild cost is the compressed 'site folder -> mount' notation, which is terse but decodable.

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?

With no output schema, the description usefully enumerates the fields a rule record carries so the agent knows what it gets back. Combined with the exclusion of amount.deliver and the uuid routing, it covers enough for a zero-parameter read tool; only scope/volume behavior is left unspecified.

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?

The tool takes no parameters, establishing the baseline of 4. The description appropriately spends its words on what the output contains instead of inventing parameter semantics, and the uuid hint correctly points to sibling tools rather than this one.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource specifically (standing folder rules) and enumerates the fields returned (site folder -> mount, schedule, mode copy/move, visibility, offloaded totals, last run), which distinguishes it clearly from a generic listing tool. The verb is implicit rather than stated ('Rules are...'), but an agent can still tell it is a read of rule records.

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 explicitly excludes one-off deliveries handled by amount.deliver and notes that rules are created in the aMount page rather than here, which is real when/when-not guidance. It also routes follow-up work to amount.files, amount.runs, and amount.measure via rule uuid, though it does not explicitly say to call this first to discover those uuids.

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