Skip to main content
Glama

List music styles

list_styles
Read-onlyIdempotent

List the genres, moods and tempos Tuney can find or generate music for.

    Call this before find_tracks or generate_track when the user names a style, and pass the
    exact values returned here.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the substantive behavioral point that this returns a canonical vocabulary whose values must be reused verbatim rather than paraphrased. It stops short of saying whether the list is static across calls, but the idempotent hint covers stability implicitly.

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?

Two short sentences, front-loaded with what the tool returns and followed by the call-ordering rule. No filler, no restatement of the title, and the actionable instruction comes second where an agent will still read it.

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?

With an output schema present, the description needn't describe return values, and with zero parameters the schema burden is minimal. The when-to-call and pass-through guidance is complete for a simple reference tool; only the stability/refresh behavior of the vocabulary is left implicit.

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?

The tool takes zero parameters, so the baseline is 4; there is no argument meaning for the description to explain. It appropriately omits parameter detail instead of padding with redundant text.

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 gives a specific verb and resource: 'List the genres, moods and tempos Tuney can find or generate music for.' The scope of the enumeration (style vocabulary) is explicit and clearly distinct from siblings such as find_tracks or generate_track, which consume these values rather than produce them.

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?

It states exactly when to call it ('before find_tracks or generate_track when the user names a style') and what to do with the result ('pass the exact values returned here'). That is explicit timing, named alternatives, and a downstream obligation, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.