Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Computers Tool

amount.computers

Lists your own and shared computers, their online status, shared folder access, quota and usage, plus site code and domains for approval checks.

Instructions

The person's own computers (the ai.artur.work program on Windows, macOS or Linux) and the ones other accounts shared with them: which are online, the folders each shares with this site (name, this site's access - read, write, or "" when not approved yet - quota and use), and this site's code. Use a computer's name as mount in amount.fetch / amount.deliver with paths "/". A folder this site may not use yet is approved by the person at that computer, who must compare the code shown there with site.code: tell them so, and try again once they allowed it. site.domains are the domains this installation serves.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful state semantics: which computers are online, that access can be read, write, or "" when not approved, and the human-approval gate that blocks use. It does not explicitly state that the call is read-only and side-effect free, nor what happens on failure.

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?

The first sentence front-loads what the tool returns, then the remaining sentences cover the mount/path convention and the approval workflow. It is dense and slightly run-on, with parentheticals stacked inside the opening sentence, but almost every clause conveys operational information.

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 helpfully enumerates return fields and their special value semantics, and it explains the approval obstacle an agent will hit. Missing: any note on result size, multiple installations, or error conditions, which are minor for a parameterless listing tool.

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?

There are zero input parameters, so the baseline is 4. The description adds value by explaining how the returned computer name is consumed as the `mount` parameter of amount.fetch and amount.deliver, which the schema cannot express.

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 a specific resource and enumerates exactly what it returns: the person's own computers and shared ones, online status, per-computer shared folders with this site's access level, quota and use, and `site.code`/`site.domains`. It could be confused with the sibling `amount.mounts`, which it never mentions or contrasts, so sibling differentiation is incomplete.

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 concrete downstream usage: use a computer's name as `mount` in amount.fetch / amount.deliver with paths of the form "<shared folder>/<path>". It also prescribes a recovery procedure when a folder is not yet approved (have the person compare the code shown there with `site.code`, then retry). It stops short of saying when to call this versus `amount.mounts` or `amount.files`.

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