Skip to main content
Glama
RagingOrangutan

rootvine-mcp

by RagingOrangutan
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

discover_music

Browse curated music collections by genre, mood, era, charts, and artist spotlights, including historic charts back to 1946, to find music for any taste.

Instructions

Browse curated music collections — charts, genre walls, moods, editorial playlists, artist spotlights, and historic charts back to 1946. Use when a user wants to EXPLORE music rather than look up a specific song or album. Examples: 'what's trending this week', 'find electronic music charts', 'show me focus playlists', 'what was number one in 1994', 'what was in the charts the year I was born'. Returns walls (collections) with their slugs, which can then be passed back as the wall argument to expand into individual tracks, albums or artists. Each entry includes a BeatsVine page URL whose streaming and purchase links can be fetched via resolve_music. Ranked by editorial pinning and refresh freshness, never by commission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallNoWall slug to drill into. If set, returns the wall's track/album/artist entries. Takes priority over `chamber`. Example: 'lastfm-top-electronic-tracks', 'deezer-90s-hits'. Slugs are returned in the foyer and chamber responses.
yearNoBrowse archived chart snapshots from this year. Use for questions about the past — 'what was number one in 1994', 'what was in the charts when I was born'. Archives run from 1946 to the present. Returns snapshot slugs; pass one back as `wall` to get the ranked entries, where position 1 is the number one. Takes priority over `chamber`.
limitNoMax items to return. Default 10, max 30. Applies to walls (foyer/chamber mode), entries (wall mode) or snapshots (year mode).
chamberNoChamber to browse. Omit for a top-level overview of all chambers and featured walls. 'by-genre' = genre corridors (house, hip-hop, jazz, etc.). 'for-this-moment' = mood and activity walls (chill, focus, workout). 'charts' = live streaming charts. 'by-era' = decades and golden eras. 'spotlights' = editor-led artist features.

Schema Changelog

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

  1. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode) or entries (wall mode)."New value: +"Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode), entries (wall mode) or snapshots (year mode)."
    • addedInput schema / properties / year
      Added value: +{
+  "description": "Browse archived chart snapshots from this year. Use for questions about the past — 'what was number one in 1994', 'what was in the charts when I was born'. Archives run from 1946 to the present. Returns snapshot slugs; pass one back as `wall` to get the ranked entries, where position 1 is the number one. Takes priority over `chamber`.",
+  "maximum": 2100,
+  "minimum": 1946,
+  "type": "integer"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full disclosure burden and does so well: it says the tool returns walls with slugs, that entries can be expanded, that streaming/purchase links require resolve_music, that year mode returns snapshots, and that results are ranked by editorial pinning and refresh freshness, not commission. These behavioral details go beyond any structured field.

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 about six purposeful sentences with the core action and scope front-loaded, then examples, return semantics, and a ranking note. No filler; each sentence adds operational or behavioral information an agent needs.

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 browse/discovery tool with four optional parameters and no output schema, the description covers how results are shaped (walls, entries, snapshots), how to drill in, how to resolve external links via a sibling, and ranking intent. There is no missing operational context an agent needs to invoke it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds value by explaining the wall-slug flow, that snapshot slugs should be passed back as wall, and that position 1 is the number one. It also frames year as the past-archive mode and chamber as the browse mode in user terms, supplementing but not repeating 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?

States a specific action ('Browse curated music collections') with concrete resource types (charts, genre walls, moods, editorial playlists, artist spotlights, historic charts). It explicitly distinguishes exploration from looking up a specific song or album and names the sibling 'resolve_music' for fetching links, so an agent can separate it from siblings.

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?

Gives an explicit use-case rule ('Use when a user wants to EXPLORE music rather than look up a specific song or album'), illustrative example queries, and a follow-up path (pass returned wall slugs back as the wall argument; use resolve_music for page links). This is clear when-to-use and alternative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RagingOrangutan/rootvine-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server