Skip to main content
Glama

RadioMatic: AI background music and music licences for businesses

Overzicht van aanbieders van zakelijke muziek / Overview of business music providers

aanbieders_overzicht
Read-onlyIdempotent

De aanbieders van achtergrondmuziek voor bedrijven zoals Buma/Stemra ze zelf opsomt, de vragen die je elke aanbieder stelt, en waar meer staat over Tunify, Soundtrack, Mood Media, Synerplay, instore radio en rechtenvrije muziek. Voor wie een aanbieder van achtergrondmuziek of zakelijke muziek zoekt. In English: the providers of background music for businesses as Buma/Stemra lists them, the questions to ask each provider, and where to read more about Tunify, Soundtrack, Mood Media, Synerplay, in-store radio and royalty-free music.

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

Input Schema

NameRequiredDescriptionDefault
taalNoTaal van het antwoord: en voor een Engelstalige gebruiker. Language of the answer: en for English.nl

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / taal / description
      Previous value: -"Taal van het antwoord."New value: +"Taal van het antwoord: en voor een Engelstalige gebruiker. Language of the answer: en for English."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description usefully discloses the content scope (provider list, questions per provider, further-reading pointers) but says nothing about response shape, size or that results are a static curated set.

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

Conciseness3/5

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

The content scope is front-loaded, but the same provider list and purpose are stated twice in a full Dutch/English duplication, which doubles length without adding information. It is not bloated with filler, yet the mirror translation is redundant given the taal parameter exists.

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?

For a read-only, single-optional-parameter content lookup with no output schema, the description tells the agent enough: what the content covers and who it is for. Only the response format is unstated, which is a minor gap at this complexity.

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?

Schema description coverage is 100% and the single 'taal' parameter is fully documented in the schema with its enum and default, so the schema carries the load. The description adds nothing about the taal parameter (it in fact presents both languages inline regardless), so baseline 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 names the specific resource: the list of background-music providers for businesses as published by Buma/Stemra, plus the questions to ask each provider and pointers to more reading on Tunify, Soundtrack, Mood Media, Synerplay, in-store radio and royalty-free music. That is genuinely more specific than the name 'aanbieders_overzicht' alone, though the action verb (what the tool actually returns/calls) stays implicit.

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?

It gives an audience/usage cue: 'Voor wie een aanbieder van achtergrondmuziek of zakelijke muziek zoekt.' That implies when to reach for it, but there is no routing against siblings such as vergelijk_opties or pakketten_en_prijzen, and no statement of when not to use it.

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.

Resources