rootvine-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_musicA | Live stream, buy and collect links for a song or album — streaming services, digital stores, vinyl and CD — ranked by trust, price and availability, never by commission. Call it rather than recall: links and prices change; a guessed link 404s. Pass the user's words as |
| resolve_gameA | Where to buy a video game. Not live yet: every call returns an explicit "coming soon" — no links, no prices — and contacts no store. Tell the user plainly that games aren't supported yet; never guess a store link or a price. For music, use resolve_music. 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. |
| find_productA | Start here when the category is unclear. Pass the user's words as |
| resolve_artistA | An artist's live profile and discography from BeatsVine, for "what else has X made" or "X's albums". Each release has a |
| discover_musicA | Browse live charts, genre and mood walls, editorial playlists, artist spotlights, and chart snapshots back to 1946 — "what's trending", "number one in 1994". Charts move weekly: call rather than recall. No arguments gives the chambers and featured walls; |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: resolving music links, resolving games (placeholder), discovering charts, resolving artists, and routing by category. find_product overlaps slightly with resolve_music and resolve_game as a meta-router, but its 'unclear category' guidance mitigates confusion. No two tools are indistinguishable.
All tool names follow a consistent snake_case verb_noun pattern: resolve_music, resolve_game, resolve_artist, discover_music, find_product. The verbs (resolve, discover, find) are clear and appropriate. No mixing of conventions.
Five tools is well-scoped for a music/game discovery and link resolution service. Each tool earns its place: three resolvers, one discoverer, and one router. Neither thin nor excessive.
For the current music-only scope, the surface is nearly complete: resolving songs/albums, discovering charts/playlists, and artist discographies. Minor gaps include album tracklists and the non-functional game resolution (explicitly marked 'coming soon'). Agents can work around these limitations.