Songs To Your Eyes — production music catalogue

Get full details for one track

stye_get_track

Read-onlyIdempotent

Everything about one cue: what it sounds like and suits, its tempo, key, length and instrumentation, every version that exists of it (stems, shorter cuts, alternate mixes) and its listen_url. For a track already found, or for what else a cue can be delivered as.

Every result carries listen_url, a permanent public page where the cue plays, with cover art and a waveform. It is the only way a person can hear a cue: a cue listed without its listen_url cannot be auditioned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ref": "<ref>"
    },
    "name": "stye_get_track"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes	The catalogue ID of a track: the `ref` field of a search or track result.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / ref / description

Previous value: -"A track ref from any other tool's results."New value: +"The catalogue ID of a track: the `ref` field of a search or track result."

First observedJul 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds meaningful context beyond that: results always carry a permanent public listen_url with cover art and waveform, and it flags the constraint that a cue without its listen_url cannot be auditioned. It does not cover failure modes for an invalid ref, but the added context is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The field inventory is front-loaded and the second paragraph focuses on the single most important output, listen_url. It is slightly verbose about the listen_url page, but every sentence is on-topic and none is filler.

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 compensates well by enumerating the returned fields and highlighting listen_url. Annotations cover the safety profile. The main omission is disambiguating against stye_list_versions, which leaves ambiguity about which tool to pick for version exploration.

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?

The single param has 100% schema description coverage, so the schema already defines 'ref' as the catalogue ID. The description only indirectly reinforces this via 'For a track already found' and does not add format, range, or lookup details. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a clear verb+resource ('Get full details for one track') and enumerates what is returned: audio character, tempo, key, length, instrumentation, versions, and listen_url. It also distinguishes itself from search by scoping to 'a track already found'. However, it never clarifies its boundary against the sibling stye_list_versions, which the description's 'every version that exists of it' seems to overlap with, leaving some ambiguity.

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?

'For a track already found, or for what else a cue can be delivered as' implies when to reach for it, but there is no explicit when-not guidance and no naming of alternatives. The overlap with stye_list_versions and stye_search_tracks is left for the agent to infer, which is a real gap given the sibling set.

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

All Songs To Your Eyes — production music catalogue tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?