Skip to main content
Glama

ampache_system

Destructive

Check Ampache connectivity, end sessions, and browse or list library indexes and now-playing data; write actions require confirm=true and allow-writes enabled.

Instructions

Ampache ping, session goodbye, index, list, browse, and now_playing. Writes run only when confirm is true and AMPACHE_ALLOW_WRITES=true. List actions default to offset 0 and limit 25 (max 500). Actions: browse, goodbye, index, list, now_playing, ping.

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_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
exactNo
limitNo
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.
includeNo
versionNo
hide_searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real context beyond that: writes are gated on confirm=true AND the AMPACHE_ALLOW_WRITES env var, and omitting confirm yields a dry-run that sends nothing. That is exactly the kind of safety detail annotations can't express. It stops short of saying what each destructive action actually destroys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The write-gating sentence is front-loaded and valuable, and the length is reasonable. But the action list is stated twice — once in the opening sentence and again in the trailing 'Actions:' clause — which is redundant padding.

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 10-parameter destructive multi-action tool with no output schema and low schema coverage, the description covers the highest-risk aspect (write gating) well. It is still incomplete on per-action behavior and on most parameters, so an agent could call it correctly for ping/list but would be guessing on browse, index, or the filter/type parameters.

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

Parameters3/5

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

Schema coverage is only 20% across 10 parameters, so the description must compensate and it only partly does: it documents confirm's semantics and the offset/limit defaults (0 and 25, max 500). Parameters such as type, exact, filter, include, version, and hide_search get no explanation in either place, leaving a substantial gap.

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

Purpose3/5

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

The description enumerates the six actions (browse, goodbye, index, list, now_playing, ping) and frames the tool as Ampache system operations, so the general purpose is visible. However, it never says what any individual action does — 'index' or 'browse' are opaque to an agent that doesn't already know Ampache — and it doesn't distinguish this tool from siblings like ampache_library or ampache_catalogs.

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

Usage Guidelines2/5

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

It gives operational preconditions for writes (confirm=true plus AMPACHE_ALLOW_WRITES=true) and list defaults, which is useful. But there is no guidance on when to pick this tool over the sibling tools, nor which action suits which situation; the agent must infer everything from the action names.

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