Skip to main content
Glama

Orb Studio music as text

get_tracks
Read-only

Songs made by Orb Studio from its news radars (geopolitics, politics, crypto, energy): title, style, mood, BPM, topics, full lyrics (Russian, German or English), cover and a listen link. You cannot hear the audio; use the text to describe a track and give listen_url.

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": "get_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax tracks (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint) and scope (openWorldHint), and the description adds a non-obvious behavioral constraint: the audio is inaccessible and only text plus listen_url should be surfaced. That is exactly the kind of context annotations cannot express. It stops short of noting volume limits or ordering, which the schema partially covers.

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 sentences, no filler: the first front-loads what a track contains, the second delivers the one operational constraint an agent must respect. The parenthetical domain and language lists are compact and informative rather than padding.

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 no output schema, the description does the work of describing the return payload field-by-field, which is the right call. The only gap is that it doesn't mention the cap of 20 tracks or default of 5 in prose, though the schema carries that.

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?

Only one parameter (limit) exists and the schema documents it fully at 100% coverage, including the default of 5 and the maximum of 20. The description adds nothing about the parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource — songs generated by Orb Studio from its news radars — and enumerates the fields each track carries (title, style, mood, BPM, topics, lyrics, cover, listen link). It does not explicitly contrast itself with nearby siblings like get_radar or get_radars, so an agent must infer the relationship between raw radar data and these derived tracks.

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?

There is an explicit directive on handling the result ('You cannot hear the audio; use the text to describe a track and give listen_url'), which is genuinely useful. However, there is no guidance on when to call this versus get_radar/get_radars, nor any exclusions, so invocation timing is only implied by the topic.

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.