Skip to main content
Glama

musicurainz

by io.github.pipeworx-io

Search Artists

search_artists
Read-onlyIdempotent

Search for music artists by name. Returns artist IDs, names, types, and countries. Use get_artist to fetch full discography and biographical details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Defaults to 10.
queryYesArtist name or search query.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesTotal number of matching artists
artistsYesList of matching artists

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "artists": {
+      "description": "List of matching artists",
+      "items": {
+        "properties": {
+          "country": {
+            "description": "Country code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "disambiguation": {
+            "description": "Disambiguation comment",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "MusicBrainz artist ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Artist name",
+            "type": "string"
+          },
+          "score": {
+            "description": "Search result relevance score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Artist type (e.g., Person, Group)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of matching artists",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "artists"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "The Beatles"
+  },
+  {
+    "limit": 5,
+    "query": "David Bowie"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-covered. The description adds value by specifying the output shape (IDs, names, types, countries) and referencing get_artist for deeper details. It does not mention pagination or rate limits, but for a simple read-only search this is adequate.

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 two sentences: the first states the action and result, the second directs to the sibling tool. It is front-loaded and contains no redundant or filler information.

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?

For a simple search tool with two parameters, detailed schema descriptions, a safe read-only annotation set, and an output schema available, the description provides all necessary context: what is searched, what is returned, and when to use a more detailed tool. No important gaps remain.

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?

The input schema already provides full descriptions for both parameters (query and limit), including the default for limit. The description adds no additional parameter-specific guidance. With schema coverage at 100%, the baseline of 3 is appropriate.

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 clearly states the action ('Search for music artists by name') and the resource (music artists), and lists the specific output fields (artist IDs, names, types, and countries). It also distinguishes the tool from the sibling get_artist by pointing out what get_artist provides, making the purpose unmistakable.

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

Usage Guidelines5/5

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

The description explicitly directs users to 'Use get_artist to fetch full discography and biographical details,' which clarifies when to choose this tool over a sibling. This provides a clear alternative and implies that this tool is for basic artist lookup, even though it does not explicitly mention search_releases.

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