rootvine-mcp

Artist discography

resolve_artist

Read-only

An artist's live profile and discography from BeatsVine, for "what else has X made" or "X's albums". Each release has a query to pass to resolve_music for its links; vinyl, CD and collector editions are album-level, so this is the route to them. Pass the artist's name as query. discography_complete: false means not yet indexed — unknown, not empty. RootVine never fabricates. Every link existed at resolved_at. Limits: UK-focused stores, prices in GBP; music only today — games are not live yet. On partial, say which sources didn't answer; on no_results, tell the user plainly — never fall back to guessing a link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`.
`query`	No	The artist's name in plain words: 'Stromae', 'Billie Eilish'. Also takes a BeatsVine artist address or an `artist/…` query from an earlier answer.

Output Schema

TableJSON Schema

Name	Required	Description
`artist`	Yes
`status`	Yes
`releases`	Yes
`resolved_as`	Yes
`resolved_at`	Yes
`did_you_mean`	Yes
`release_count`	Yes
`discography_complete`	Yes	false: BeatsVine has not indexed this artist yet — an empty list means unknown, not none

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 26, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "The artist's name in plain words: 'Stromae', 'Billie Eilish'. Also takes a BeatsVine artist address or an `artist/…` query from an earlier answer.",
+  "maxLength": 500,
+  "type": "string"
+}

changedInput schema / properties / slug / description

Previous value: -"The BeatsVine artist slug, lowercase and hyphenated: 'stromae', 'radiohead', 'ed-sheeran'. Slugs keep letters of any script, so non-Latin names are valid. An 'artist/name' form is also accepted, since that is what BeatsVine's search returns for artist hits."New value: +"Deprecated alias for `query`, kept for older clients. Send exactly one of `query` or `slug`."

addedInput schema / properties / slug / maxLength
```
Added value: +500
```
removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "artist": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "genres": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "name": {
+              "type": "string"
+            },
+            "page_url": {
+              "type": "string"
+            },
+            "query": {
+              "description": "Pass back to resolve_artist to open this artist",
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "query",
+            "page_url",
+            "genres"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "did_you_mean": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "artist": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "kind": {
+            "enum": [
+              "track",
+              "album",
+              "artist"
+            ],
+            "type": "string"
+          },
+          "page_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "query": {
+            "description": "Pass back as `query` to open exactly this",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "artist",
+          "kind",
+          "query",
+          "page_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "discography_complete": {
+      "description": "false: BeatsVine has not indexed this artist yet — an empty list means unknown, not none",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "release_count": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "releases": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cover_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "page_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "query": {
+            "description": "Pass to resolve_music for this release's links",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "title",
+          "type",
+          "year",
+          "query",
+          "page_url",
+          "cover_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "resolved_as": {
+      "additionalProperties": {},
+      "properties": {
+        "corrected": {
+          "description": "The answer is for different words than asked: tell the user what is shown",
+          "type": "boolean"
+        },
+        "note": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "query": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "via": {
+          "anyOf": [
+            {
+              "enum": [
+                "direct",
+                "catalogue_search",
+                "live_lookup"
+              ],
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "required": [
+        "query",
+        "via",
+        "corrected",
+        "note"
+      ],
+      "type": "object"
+    },
+    "resolved_at": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "success",
+        "no_results"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "artist",
+    "discography_complete",
+    "release_count",
+    "releases",
+    "resolved_as",
+    "did_you_mean",
+    "resolved_at"
+  ],
+  "type": "object"
+}

First observedSep 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds significant context beyond them: 'RootVine never fabricates', 'Every link existed at resolved_at', the meaning of discography_complete: false as unknown not empty, and explicit handling instructions for partial and no_results cases. This enriches the agent's understanding of data reliability and response handling without contradicting annotations.

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?

The description is moderately long but every sentence carries weight: purpose, release linkage, index state, data integrity, store limits, and failure handling. It is front-loaded with the core purpose and then layers constraints, so the structure is effective and not wasteful.

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 output schema exists, the description covers all essential operational aspects: how to call it (artist name in query), what the output implies (each release has a query), limitations (UK stores, GBP, music only), and behavior on partial/no_results. The agent can use it correctly without missing critical context.

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%, so the schema already explains both parameters. The description reinforces that the artist name goes in `query` and that slug is deprecated, but it does not introduce new parameter meaning beyond what the schema provides. Baseline 3 applies because the description adds little extra semantic value.

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 states a specific verb+resource: 'An artist's live profile and discography from BeatsVine'. It names the intended queries ('what else has X made' or 'X's albums') and distinguishes from siblings by pointing out that each release carries a query for resolve_music and that album-level editions are routed here.

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 gives clear context on when to use the tool (artist discography needs) and even directs album-level editions to this route. It also notes that games are not live, hinting at resolve_game. However, it does not explicitly state 'use resolve_music for individual tracks' or when NOT to use this tool, though the mention of resolve_music implies a division of labor.

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

All rootvine-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.