score_transition
Score how well one catalog track mixes into another (0-100) — the pairwise DJ transition score no raw key/BPM API gives you. Combines Camelot-wheel key compatibility, octave-aware BPM proximity (half/double-time counts as a match), and energy smoothness. Returns the overall score, per-component s...
This record as markdown: /tools/com-freqblog-music-metadata/score-transition.md
What score_transition does on FreqBlog Music Metadata
AI agents call score_transition to retrieve information from FreqBlog Music Metadata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to_track_id | string | Yes | The candidate track you're mixing INTO — a catalog itunes_track_id. |
from_track_id | string | Yes | The track you're mixing FROM — a catalog itunes_track_id, e.g. 'apple_ad1829eeccb70f9a'. |
Parameters from the server's own tool schema.
Why score_transition is rated Low
The tool reads metadata about two tracks (keys, BPM, energy) and computes a compatibility score through algorithmic analysis. It returns analytical results without creating, modifying, deleting data or executing code. This is fundamentally a read-only analysis operation with no side effects.
From the tool's definition Tool performs scoring and analysis of track compatibility data ('Score how well one catalog track mixes into another', returns 'score', 'per-component scores', 'detail block', 'reason') — a calculation and retrieval operation with no modification, deletion,…
Attacks that exploit this kind of access
The rule that runs score_transition safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FreqBlog Music Metadata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For score_transition, this is the rule to start with:
score_transition is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FreqBlog Music Metadata, apply this rule, and every score_transition call is checked against it from then on.
Questions about score_transition
Score how well one catalog track mixes into another (0-100) — the pairwise DJ transition score no raw key/BPM API gives you. Combines Camelot-wheel key compatibility, octave-aware BPM proximity (half/double-time counts as a match), and energy smoothness. Returns the overall score, per-component scores (harmonic/tempo/energy), a detail block (key_relation, both Camelot keys, both BPMs, bpm_delta, bpm_octave_matched, both energies, energy_delta), and a one-line human reason (e.g. "8A->9A adjacent (+1), 126->128 BPM (+2), energy +0.04 — clean uplifting mix"). Both ids are catalog itunes_track_ids — get them from search_catalog or the itunes_track_id field of a get_audio_features result. Costs 1 quota unit. It is categorised as a Read tool in the FreqBlog Music Metadata MCP Server, which means it retrieves data without modifying state.
score_transition accepts 2 parameters: to_track_id, from_track_id. Required: to_track_id, from_track_id. The full parameter table on this page comes from the server's own tool schema.
Register the FreqBlog Music Metadata MCP server in PolicyLayer and add a rule for score_transition: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches FreqBlog Music Metadata. Nothing to install.
score_transition is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the score_transition rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for score_transition. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
score_transition is provided by the FreqBlog Music Metadata MCP server (https://mcp.freqblog.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FreqBlog Music Metadata, and thousands of servers like it.
This server
Across the catalogue