Skip to main content
Glama

ampache_users

Destructive

Manage Ampache users and their preferences: list, create, edit, delete accounts, and get or set user and system preferences; write actions require confirmation.

Instructions

Users and preferences (admin): list, get, create, edit, delete, and preference get/set. Passwords are never logged. Writes run only when confirm is true and AMPACHE_ALLOW_WRITES=true. List actions default to offset 0 and limit 25 (max 500). Actions: preference_create, preference_delete, preference_edit, system_preference, system_preferences, user, user_create, user_delete, user_edit, user_preference, user_preferences, users.

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": {
      "action": "<action>"
    },
    "name": "ampache_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
typeNo
emailNo
groupNo
levelNo
limitNo
stateNo
valueNo
accessNo
actionYesAmpache operation to call.
filterNo
offsetNo
confirmNoBoolean true runs the write when AMPACHE_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
defaultNo
disableNo
websiteNo
categoryNo
fullnameNo
passwordNo
usernameNo
maxbitrateNo
clear_statsNo
descriptionNo
subcategoryNo
reset_apikeyNo
fullname_publicNo
reset_streamtokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: writes are double-gated by confirm and an environment flag, omitted/false confirm yields a dry-run that sends nothing, passwords are never logged, and list actions are paginated with default 25 and a 500 max. It does not describe return shapes, but that is partly covered by the action naming.

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 tight sentences: purpose first, then the safety constraint, then pagination and the action enumeration. No filler, and the most consequential information (write gating) is front-loaded before the long action list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-action, 27-parameter destructive tool with no output schema, the description covers gating and pagination but leaves the per-action parameter contract entirely undocumented, so an agent knows the safety model yet cannot reliably infer which fields to supply for user_create versus preference_edit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 7% across 27 parameters, so the description carries most of the burden. It explains confirm (including that the string "true" is rejected, which is in the schema) and offset/limit defaults, but says nothing about the many user and preference fields (username, password, access, level, reset_apikey, clear_stats, category, subcategory, etc.) or which parameters each action requires.

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 opens with a specific resource and scope ("Users and preferences (admin)") and enumerates the operations (list, get, create, edit, delete, preference get/set), then lists the full action enum. This clearly separates it from sibling domains like catalogs, playlists or system, although no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the action list and the write gating rule (confirm=true plus AMPACHE_ALLOW_WRITES=true), which tells the agent how to trigger a write versus a dry-run preview. However, there is no guidance on when to prefer this tool over ampache_system for the system_preference actions, nor which action to choose for a given intent.

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