Skip to main content
Glama

diggercamp

by com.diggercamp

generate_playlist

Generate and SAVE a playlist to the user's diggercamp account. It starts from a seed track and develops the set from there (energy and genre flow), optionally ending on a chosen track. Requires the user to be signed in to diggercamp. - url: seed track link (Bandcamp / YouTube / SoundCloud) — the playlist starts here. - n: number of tracks, 5 to 30 (default 15). - end_url: optional link of the track to END on. - vibe: optional one of warm_up, afterhours, yoga, focus, sunset (shapes the energy curve).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
urlYes
vibeNo
end_urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate non-read-only (readOnlyHint=false) and non-destructive (destructiveHint=false), and the description adds that the tool saves to the user's account and requires sign-in. It also explains the energy flow and vibe shaping. No contradiction with annotations.

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 concise: three sentences plus a bulleted list. Each bullet covers one parameter. No redundant information. The main action is front-loaded, and the structure is easy to parse.

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

Completeness4/5

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

Given the tool’s complexity (generation, saving, multiple parameters, vibe), the description covers prerequisites, parameter meanings, and core behavior. Output schema exists to document return values, so omission is acceptable. However, it could mention error handling (e.g., invalid URL) for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries full burden. It explains url as a seed track link with specific platforms, n with range 5-30 and default, end_url as optional ending track, and vibe with allowed values and effect on energy curve. This adds significant meaning 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 clearly states the tool 'Generate and SAVE a playlist' from a seed track with energy and genre flow. It distinguishes itself from sibling tools like find_similar or inspire_me by emphasizing full playlist generation and saving to an account.

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

Usage Guidelines3/5

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

The description mentions the prerequisite of being signed in but does not explicitly guide when to use this tool versus alternatives. Sibling tools like deep_match or surprise_me are not referenced, leaving the agent to infer usage context from the action of saving.

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

All diggercamp 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.7/5.0
Disambiguation4/5

Most tools have distinct purposes: deep_match for technical DJ matching, find_similar for general sonic similarity, generate_playlist for creating full sets, inspire_me for personalized discovery, playlist_match for multi-track centroid matching, and surprise_me for broad discovery. However, inspire_me and surprise_me both relate to discovery with overlap in scope, causing minor ambiguity.

Naming Consistency3/5

Tool names use a mix of verbs and descriptive phrases (deep_match, find_similar, generate_playlist, inspire_me, playlist_match, surprise_me). The pattern is not fully consistent; some use verb_noun (generate_playlist) while others use verb_adjective (find_similar) or are more abstract (inspire_me). Not chaotic but lacks a uniform structure.

Tool Count5/5

6 tools is well-scoped for a music discovery server. Each tool covers a specific function without redundancy, covering technical matching, similarity search, playlist generation, personalized discovery, group matching, and broad exploration. The number feels balanced and appropriate.

Completeness4/5

The tools cover core music discovery workflows: single-track matching, multi-track centroid matching, playlist generation with energy flow, and personalized/random discovery. Minor gaps include lack of explicit CRUD for user playlists beyond generation and no tools for browsing or managing user history directly.

Resources