Dynamoi

Check Distribution Application

dynamoi_get_distribution_application

Read-only

Use this for "get my music on Spotify" or "distribute my song": Dynamoi distributes to 100+ stores and artists keep 90% of net receipts. Use this when the user asks whether an artist qualifies for Dynamoi music distribution, wants the five application requirements, or wants the status of an existing distribution application. It checks Spotify connection, at least 1,000 Spotify followers, at least 10,000 verified monthly listeners, connected Facebook Page plus Instagram professional identity, and a connected YouTube channel. Meeting all five requirements permits an application but never guarantees approval. When the connection tools are available, use purpose=distribution_identity for missing Meta or YouTube identity; otherwise tell the user: 'You can do this in the Dynamoi dashboard at https://dynamoi.com/dashboard.' Identity connections do not require advertising billing.

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": {
      "artistId": "<artistId>"
    },
    "name": "dynamoi_get_distribution_application"
  }
}

Input Schema

Name	Required	Description	Default
`artistId`	Yes

Output Schema

Name	Required	Description	Default
`code`	No
`data`	No
`kind`	No
`field`	No
`status`	Yes
`draftId`	No
`message`	No
`retryable`	No
`nextAction`	No
`failureStage`	No
`prerequisite`	No
`screeningResult`	No
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / properties / code / enum

Previous value: -[
-  "ACCOUNT_READ_ONLY",
-  "INVALID_SPOTIFY_SOURCE",
-  "CAPABILITY_REQUIRED",
-  "INSUFFICIENT_SCOPE",
-  "STATE_CONFLICT",
-  "QUOTE_CHANGED",
-  "RATE_LIMITED",
-  "OUTPUT_INVALID",
-  "UNKNOWN_EFFECT"
-]New value: +[
+  "ACCOUNT_READ_ONLY",
+  "INVALID_SPOTIFY_SOURCE",
+  "CAPABILITY_REQUIRED",
+  "INSUFFICIENT_SCOPE",
+  "TENANT_ACCESS_DENIED",
+  "STATE_CONFLICT",
+  "QUOTE_CHANGED",
+  "RATE_LIMITED",
+  "OUTPUT_INVALID",
+  "UNKNOWN_EFFECT"
+]

Changed3 schema fields changedSep 24, 2026

addedOutput schema / properties / draftId

Added value: +{
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

addedOutput schema / properties / failureStage

Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / screeningResult

Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

Changed2 schema fields changedSep 23, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed2 schema fields changedSep 20, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedOutput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

Changed6 schema fields changedSep 10, 2026

addedOutput schema / properties / code

Added value: +{
+  "enum": [
+    "ACCOUNT_READ_ONLY",
+    "INVALID_SPOTIFY_SOURCE",
+    "CAPABILITY_REQUIRED",
+    "INSUFFICIENT_SCOPE",
+    "STATE_CONFLICT",
+    "QUOTE_CHANGED",
+    "RATE_LIMITED",
+    "OUTPUT_INVALID",
+    "UNKNOWN_EFFECT"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / field

Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / nextAction

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "field": {
+      "maxLength": 120,
+      "minLength": 1,
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "provide_input",
+        "read_status",
+        "reconnect",
+        "handoff"
+      ],
+      "type": "string"
+    },
+    "reason": {
+      "maxLength": 240,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / prerequisite

Added value: +{
+  "maxLength": 240,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / retryAfterSeconds

Added value: +{
+  "maximum": 86400,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```

AddedAug 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered, and the description goes well beyond them by enumerating the five checks performed and clarifying that meeting all five only permits an application, not approval. It does not discuss rate limits or response shape, but the output schema covers returns, so this is strong without being exhaustive.

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 trigger phrases and core capability are front-loaded, and the requirement list is compact. The paragraph is dense and runs long, but each sentence carries routing or eligibility information rather than filler.

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 read-only eligibility check with an output schema handling the return values, the description covers what the tool does, when to invoke it, what it verifies, the limits of its verdict, and what to do when dependent tools are missing. Nothing needed to call it correctly is absent.

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 0% and the description never mentions the single artistId parameter, so it adds no semantic detail beyond the schema. The parameter is nonetheless self-describing (a UUID artist identifier) and there is only one, which keeps the practical gap small.

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

Purpose5/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: it checks whether an artist qualifies for Dynamoi distribution, enumerates the five requirements, and reports the status of an existing application. It is clearly separable from siblings like dynamoi_apply_for_distribution, which the 'permits an application but never guarantees approval' line implicitly positions as the follow-on action.

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 names the exact user phrasings that should trigger it ('get my music on Spotify', 'distribute my song') and the question types it answers (qualification, requirement list, application status). It also routes the agent to a sibling path (purpose=distribution_identity for missing Meta/YouTube identity) and supplies an explicit fallback message and dashboard URL when those tools are unavailable.

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

All Dynamoi 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.