Skip to main content
Glama

AINSOF

by io.ainsof.mcp
OverviewDiscussionsAdmin

search_music

Use this when the user needs existing, licensable music or sound effects for a project — background music, production music, music for an ad, trailer, YouTube video, podcast, game or film — described in words (mood, scene, genre, instruments, energy). Do not use it to generate new music, write lyrics, identify a song, or play commercial releases by other artists. Find AINSOF music from a written brief — mood, scene, genre, energy, instruments. Example: 'lo-fi hip hop underscore, warm, no vocals'. Send the user's original language and musical intent, including durations and exclusions. Each call is self-contained. For a refinement, combine the current musical requirements and the latest change into brief; do not send only the clarification question. Send only musical requirements, never chat transcripts, assistant replies or unrelated personal information. Pass the customer's musical request in their original language, preserving their words, exclusions and durations. Do not add instruments, genres, mood, energy or vocal restrictions that they did not ask for. For a refinement, combine only the customer's established requirements and latest change, not suggestions from an assistant. One search returns evaluated matches or alternatives; present that result before proposing another direction. An unavailable search is a technical failure, not an empty catalog: explain it and do not automatically repeat or broaden the request. A user-requested retry remains possible. Use the returned understanding, followups and selected preview version when presenting the answer. A NAME also works, and is answered exactly: pass a track title ('Shine On Today'), an album ('Shining Ahead'), a catalog number ('AIN-CAT 031') or a COMPOSER ('Alon Peretz') as the brief and you get that cue, that album in full, or everything that writer wrote. A composer named inside an ordinary brief puts their cues first without narrowing it. NEVER tell a user we do not have a track until you have passed its name here.

Input Schema

NameRequiredDescriptionDefault
briefYesWhat the music should be — or the exact name of a track, album or catalog number.
scopeNoOptional library restriction; omit to let the request select the library.
top_kNoNumber of candidates requested. Discovery searches normalize values below eight to eight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / top_k / default
      Previous value: -10New value: +8
    • addedInput schema / properties / top_k / description
      Added value: +"Number of candidates requested. Discovery searches normalize values below eight to eight."
  2. Changed1 schema field changed
    • changedInput schema / properties / brief / description
      Previous value: -"What the music should be — or the exact name of a track, album or catalogue number."New value: +"What the music should be — or the exact name of a track, album or catalog number."
  3. Changed3 schema fields changed
    • removedInput schema / properties / clarification
      Removed value: -{
-  "maxLength": 500,
-  "type": "string"
-}
    • removedInput schema / properties / continue_previous
      Removed value: -{
-  "type": "boolean"
-}
    • removedInput schema / properties / history
      Removed value: -{
-  "description": "Only the current search conversation, in order. Include the original user brief; mark its first user turn contextStart=true. Exclude older topics.",
-  "items": {
-    "properties": {
-      "answerTo": {
-        "maxLength": 500,
-        "type": "string"
-      },
-      "contextStart": {
-        "description": "True on the first user turn of the active search topic.",
-        "type": "boolean"
-      },
-      "role": {
-        "enum": [
-          "user",
-          "assistant"
-        ],
-        "type": "string"
-      },
-      "text": {
-        "maxLength": 600,
-        "type": "string"
-      }
-    },
-    "required": [
-      "role",
-      "text"
-    ],
-    "type": "object"
-  },
-  "maxItems": 8,
-  "type": "array"
-}
  4. Changed6 schema fields changed
    • addedInput schema / properties / clarification
      Added value: +{
+  "maxLength": 500,
+  "type": "string"
+}
    • addedInput schema / properties / continue_previous
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / history
      Added value: +{
+  "description": "Only the current search conversation, in order. Include the original user brief; mark its first user turn contextStart=true. Exclude older topics.",
+  "items": {
+    "properties": {
+      "answerTo": {
+        "maxLength": 500,
+        "type": "string"
+      },
+      "contextStart": {
+        "description": "True on the first user turn of the active search topic.",
+        "type": "boolean"
+      },
+      "role": {
+        "enum": [
+          "user",
+          "assistant"
+        ],
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 600,
+        "type": "string"
+      }
+    },
+    "required": [
+      "role",
+      "text"
+    ],
+    "type": "object"
+  },
+  "maxItems": 8,
+  "type": "array"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Optional library restriction; omit to let the request select the library.",
+  "enum": [
+    "music",
+    "sfx"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / top_k / maximum
      Added value: +40
    • addedInput schema / properties / top_k / minimum
      Added value: +1
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important operating behavior: calls are self-contained, refinements must combine prior requirements with the latest change, unavailable searches are technical failures rather than empty catalogs, and automatic repetition or broadening is discouraged. These are substantial behavioral details not conveyed by the structured hints.

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 description is front-loaded with purpose and exclusions, but it is long and repetitive, especially around refinements and preserving the user's original wording. Several sentences could be merged without losing guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex search tool with no output schema, the description covers brief construction, name lookup, failure handling, refinement behavior, and how to use returned understanding/followups/previews. It is complete enough for an agent to invoke and present results correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description meaningfully enriches the brief parameter by specifying that the user's original language and musical intent must be preserved, that exclusions and durations should be included, and that exact names, album titles, catalog numbers, and composers are valid inputs.

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 specific verb and resource: find/search AINSOF music and sound effects from a written brief, including exact track/album/composer lookup. It clearly excludes generation, lyric writing, song identification, and playing commercial releases, though it does not explicitly distinguish itself from sibling search tools such as search_by_reference or find_similar.

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 gives explicit when-to-use guidance, when-not-to-use exclusions, and examples of acceptable briefs. It also specifies how to handle refinements, retries, and technical failures versus empty results, leaving little to inference.

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

All AINSOF toolsInspect
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