Skip to main content
Glama
h-3303

flacli

by h-3303
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wiki_write

Writes plain-text artist or album notes to a sidecar file beside the music and pushes them into the player cache, with source attribution and optional replacement.

Instructions

Store the text for an artist (album=None) or an album: written to a sidecar file beside the music and pushed into the player's cache. Plain text, no markup; one paragraph for an album, two for an artist; only what the sources support. attribution is shown under the text: name the sources and, if you wrote it, yourself (e.g. "Written by Claude from MusicBrainz and Discogs, 2026-09-17"). force replaces existing text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
albumNo
forceNo
artistYes
contentYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.9/5.0
Behavior1/5

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

Annotations declare destructiveHint=false, but the description says 'force replaces existing text,' which describes a destructive overwrite. This directly contradicts the annotation, forcing a score of 1 under the contradiction rule.

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?

A single dense paragraph that front-loads the action and destination. The attribution example earns its place, though the semicolon-heavy structure is slightly run-on.

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 6-parameter write tool with no output schema and 0% schema descriptions, the description covers most behavioral and content requirements. However, it leaves url undocumented and gives no sibling-usage routing.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains album=None, content formatting rules, attribution format, and force behavior, but it omits the url parameter entirely.

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?

States a specific verb ('Store') and resource ('text for an artist (album=None) or an album'), with a clear sidecar/cache destination. It does not explicitly differentiate itself from sibling wiki tools such as wiki_fill or wiki_sources, so it falls short of a 5.

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?

Provides formatting, content, and attribution rules, but does not say when to use this tool versus alternatives like wiki_fill or wiki_sources. No prerequisites, exclusions, or routing guidance are given.

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

Deploy Server

Other Tools