Skip to main content
Glama

musicurainz

by io.github.pipeworx-io

Get Release

get_release
Read-onlyIdempotent

Get release details: full track listing, credits, media formats, and metadata. Requires release ID from search_releases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMusicBrainz release ID (UUID).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMusicBrainz release ID
dateNoRelease date (YYYY-MM-DD)
titleYesRelease title
statusNoRelease status
tracksYesList of tracks on release
artist_creditYesArtist credits for release

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "0cfb11b7-90b9-46d4-8910-e1d39f7f5fa0"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "artist_credit": {
+      "description": "Artist credits for release",
+      "items": {
+        "properties": {
+          "artist_id": {
+            "description": "MusicBrainz artist ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Artist name as credited",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "date": {
+      "description": "Release date (YYYY-MM-DD)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "MusicBrainz release ID",
+      "type": "string"
+    },
+    "status": {
+      "description": "Release status",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Release title",
+      "type": "string"
+    },
+    "tracks": {
+      "description": "List of tracks on release",
+      "items": {
+        "properties": {
+          "length_ms": {
+            "description": "Track duration in milliseconds",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "number": {
+            "description": "Track number",
+            "type": "string"
+          },
+          "position": {
+            "description": "Track position on media",
+            "type": "number"
+          },
+          "title": {
+            "description": "Track title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "position",
+          "number",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "artist_credit",
+    "tracks"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "name": "requests",
-    "version": "2.31.0"
-  },
-  {
-    "name": "flask",
-    "version": "3.0.0"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "author": {
-      "description": "Package author name",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "files": {
-      "description": "Release distribution files",
-      "items": {
-        "properties": {
-          "filename": {
-            "description": "Distribution filename",
-            "type": "string"
-          },
-          "packagetype": {
-            "description": "Package type (e.g., sdist, bdist_wheel)",
-            "type": "string"
-          },
-          "sha256": {
-            "description": "SHA256 hash digest",
-            "type": "string"
-          },
-          "size": {
-            "description": "File size in bytes",
-            "type": "number"
-          },
-          "upload_time": {
-            "description": "Upload timestamp",
-            "type": "string"
-          },
-          "url": {
-            "description": "Download URL",
-            "type": "string"
-          }
-        },
-        "required": [
-          "filename",
-          "packagetype",
-          "upload_time",
-          "size",
-          "url",
-          "sha256"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "license": {
-      "description": "License type",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "description": "Package name",
-      "type": "string"
-    },
-    "requires_dist": {
-      "description": "Package dependencies",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "requires_python": {
-      "description": "Python version requirement",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "summary": {
-      "description": "Short package description",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "version": {
-      "description": "Release version number",
-      "type": "string"
-    }
-  },
-  "required": [
-    "name",
-    "version",
-    "summary",
-    "author",
-    "license",
-    "requires_python",
-    "requires_dist",
-    "files"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "description": "Package author name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "files": {
+      "description": "Release distribution files",
+      "items": {
+        "properties": {
+          "filename": {
+            "description": "Distribution filename",
+            "type": "string"
+          },
+          "packagetype": {
+            "description": "Package type (e.g., sdist, bdist_wheel)",
+            "type": "string"
+          },
+          "sha256": {
+            "description": "SHA256 hash digest",
+            "type": "string"
+          },
+          "size": {
+            "description": "File size in bytes",
+            "type": "number"
+          },
+          "upload_time": {
+            "description": "Upload timestamp",
+            "type": "string"
+          },
+          "url": {
+            "description": "Download URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "filename",
+          "packagetype",
+          "upload_time",
+          "size",
+          "url",
+          "sha256"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "license": {
+      "description": "License type",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Package name",
+      "type": "string"
+    },
+    "requires_dist": {
+      "description": "Package dependencies",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "requires_python": {
+      "description": "Python version requirement",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "description": "Short package description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version": {
+      "description": "Release version number",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "version",
+    "summary",
+    "author",
+    "license",
+    "requires_python",
+    "requires_dist",
+    "files"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "requests",
+    "version": "2.31.0"
+  },
+  {
+    "name": "flask",
+    "version": "3.0.0"
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the specific data returned (track listing, credits, media formats, metadata), which goes beyond the schema and annotations. No contradiction exists.

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?

The description is a single concise sentence that front-loads the core purpose and includes useful specifics without redundancy. Every phrase earns its place, and there is no filler or repetition of annotations.

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

Completeness5/5

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

Given the simple single-parameter input, rich annotations, and presence of an output schema, the description sufficiently covers all needed context. It states the prerequisite, the contents of the response, and the overall purpose, making the tool fully usable without additional information.

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 description coverage is 100% for the single 'id' parameter, which is fully described as a MusicBrainz release ID (UUID). The description reinforces this by mentioning the ID comes from search_releases, but adds no new semantic information beyond the schema.

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

Purpose5/5

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

The description uses a specific verb and resource ('Get release details') and lists concrete contents (full track listing, credits, media formats, metadata). It clearly differentiates from siblings like get_artist and search_releases by specifying the release-specific data and the prerequisite ID source.

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?

The description states 'Requires release ID from search_releases,' which clearly indicates the intended workflow and when to use this tool (after obtaining an ID from search_releases). It does not explicitly name alternatives or exclusion conditions, but the usage context is clear and actionable.

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

All musicurainz toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Many tools are crisply separated (memory CRUD, subscription lifecycle, single-entity vs compare vs profile), but several broad entry points overlap: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are very close variants, and discover_tools/suggest_questions/ask_pipeworx all serve discovery/routing. Descriptions help, but an agent can still easily select one of the duplicate or adjacent tools instead of the intended one.

Naming Consistency3/5

All names are readable snake_case and there are coherent families (polymarket_*, ask_pipeworx_*, search_*, get_*), but there is no consistent verb_noun convention: noun-phrase names like recent_alerts and pipeworx_trending coexist with single verbs like remember and forget and domain-prefixed nouns like polymarket_edges. Mixed, but still reasonably navigable.

Tool Count2/5

At 35 tools, the surface is well past the comfortable 3-15 tool scope and even beyond the 16-25 heavy range unless the server has one explicit mega-purpose. The set also sprawls across music lookup, Pipeworx research, prediction markets, npm checks, LLM visibility, memory, and subscriptions, so no single coherent job emerges.

Completeness4/5

For the dominant read-only research workflow, the set is remarkably complete: discover tools, grounded and ungrounded asking, deep research, entity resolution, profiles, recent changes, comparisons, claim verification, search_within, plus full memory and subscription lifecycles. Minor gaps include the shallow music side relative to the rest of the server and the absence of an explicit source catalog.

Resources