Skip to main content
Glama

Dynamoi

by io.github.getDynamoi

Get Account Overview

dynamoi_get_account_overview
Read-only

Use this when the user explicitly asks about the signed-in Dynamoi account itself, such as who is logged in, how many organizations or artists it can access, or whether account-level platform connections exist. Always pass intent to match that explicit account question. Do not use this to confirm a specific Meta or YouTube onboarding attempt because this account-level state can span multiple artists; use dynamoi_get_platform_status for the target artist instead. Do not use this to enumerate artists one by one; use dynamoi_list_artists for that. Never use this to 'check context' before answering generic Instagram, lyrics, songwriting, or marketing-advice questions, even if Dynamoi is attached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNo
intentYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
kindNo
statusYes
messageNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • addedOutput schema / properties / data / properties / artistCount
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / data / properties / artists
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "summaries": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "publicUrl": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "summaries"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / data / properties / organizationCount
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / data / properties / recommendedNextActions
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / properties / state
      Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
    • addedOutput schema / properties / data / properties / summary
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / data / properties / user
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / kind / enum
      Removed value: -[
-  "validation",
-  "business",
-  "platform",
-  "unknown"
-]
  2. Changed4 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +false
    • addedOutput schema / properties / data
      Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
    • addedOutput schema / properties / kind
      Added value: +{
+  "enum": [
+    "validation",
+    "business",
+    "platform",
+    "unknown"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / message
      Added value: +{
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "status": {
+      "enum": [
+        "success",
+        "partial_success",
+        "error"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only behavior is covered. The description adds useful contextual behavior: account-level state can span multiple artists, making this tool inappropriate for single-artist platform confirmation. It could go further by describing what the returned overview contains, but the output schema likely covers that.

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

Conciseness5/5

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

The description is front-loaded with the core use case, then provides precise exclusions and alternatives. Every sentence earns its place; there is no filler or vague boilerplate.

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?

Given the output schema exists, the description does not need to explain return values. It fully covers invocation conditions, required intent behavior, exclusions, and sibling routing, which is complete for a read-only account-overview tool.

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 description coverage is 0%, so the description must compensate. It does so for the required intent parameter by explaining that it should match the explicit account question, and the prose lists the relevant concerns (organizations, artists, platform connections) that map to the intent enum. The optional format parameter is not discussed, but json/summary are self-explanatory.

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 names a specific verb and resource: it is for explicit questions about the signed-in Dynamoi account itself (who is logged in, organizations/artists accessible, account-level platform connections). It also explicitly distinguishes itself from sibling tools like dynamoi_list_artists and dynamoi_get_platform_status, so there is no ambiguity about what this tool is for.

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?

The description gives crystal-clear when-to-use guidance and equally clear when-not-to-use guidance. It names the exact alternatives (dynamoi_get_platform_status for artist-specific onboarding, dynamoi_list_artists for enumeration) and explicitly forbids using this tool as a generic context-check before answering unrelated questions.

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

All Dynamoi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools are cleanly separated by resource and action, and close pairs like account overview vs platform status and singular vs catalog smart-link creation are explicitly disambiguated. The main ambiguity is dynamoi_search versus the connector search tool, which both search the same entities and are distinguished only by chat vs deep-research context.

Naming Consistency4/5

The set overwhelmingly follows a consistent dynamoi_<verb>_<object> snake_case pattern, with predictable get/list/create/update verbs. The unprefixed fetch and search connector tools are a visible but small deviation from that convention.

Tool Count3/5

Seventeen tools is slightly heavy for the server's scope, especially since search/fetch partly duplicate dynamoi_search and the campaign domain is primarily read-only. The smart-link, artist, and distribution clusters each justify their tools, so it is not excessively bloated.

Completeness3/5

Smart links have create/list/get/update coverage and distribution has apply/status, but campaigns are only readable with no create/update/launch tool, despite get_campaign referencing campaign mutations. Platform connections also have status checks but no connect actions, leaving notable workflow gaps.

Resources