Skip to main content
Glama

ampache_shares

Destructive

List, fetch, create, edit, or delete Ampache media share links; write actions require explicit confirmation and share tokens are redacted.

Instructions

Shares: list, get, create, edit, and delete. Share tokens are redacted. Writes run only when confirm is true and AMPACHE_ALLOW_WRITES=true. List actions default to offset 0 and limit 25 (max 500). Actions: share, share_create, share_delete, share_edit, shares.

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

Input Schema

NameRequiredDescriptionDefault
addNo
condNo
sortNo
typeNo
exactNo
limitNo
actionYesAmpache operation to call.
filterNo
offsetNo
updateNo
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.
expiresNo
descriptionNo
max_counterNo
allow_streamNo
allow_downloadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations (destructive=true, readOnly=false, openWorldHint=true), the description discloses two genuinely useful traits: share tokens are redacted in output, and writes are gated behind confirm plus an environment flag, implying a dry-run default. It stops short of saying whether deletes are permanent or what a destructive call removes, which is the main remaining gap.

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?

Four short sentences, front-loaded with the resource and operations, followed by safety mechanics and defaults. The trailing action enumeration partly duplicates the schema enum but usefully names the concrete values; little is wasted.

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

Completeness2/5

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

For a 16-parameter, action-multiplexed, destructive tool with no output schema and very low schema description coverage, the definition covers safety gating and token redaction but leaves most parameters and their per-action relevance unexplained. An agent can call it but cannot confidently construct create/edit payloads.

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 13%, so the description carries most of the burden and does explain action, confirm, offset, and limit semantics (defaults 0/25, max 500). The other twelve parameters (add, cond, sort, type, exact, filter, update, expires, description, max_counter, allow_stream, allow_download) are left entirely undefined in both schema and description, so the agent cannot tell which parameters apply to which action.

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 ('Shares') and enumerates the operations it supports (list, get, create, edit, delete), then maps them to concrete action values (share, shares, share_create, share_edit, share_delete), so an agent can match intent to tool. It does not explicitly differentiate itself from the sibling domain tools, but the resource scope is unambiguous.

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?

It gives a real prerequisite for writes (confirm=true plus AMPACHE_ALLOW_WRITES=true) and states list defaults and caps, which tells the agent how to call it safely. However, it offers no when-to-use/when-not guidance relative to sibling tools such as ampache_playlists or ampache_library, leaving routing to be inferred from the resource name.

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