Skip to main content
Glama

Dynamoi

by io.github.getDynamoi
OverviewDiscussionsAdmin

Search (OpenAI Connectors)

search
Read-only

OpenAI ChatGPT Deep Research / Connectors search contract. Returns matching Dynamoi artists, campaigns, and Smart Links so they can be cited in a deep-research session. For regular ChatGPT chat use dynamoi_search instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNo
dataNo
kindNo
fieldNo
statusYes
draftIdNo
messageNo
retryableNo
nextActionNo
failureStageNo
prerequisiteNo
screeningResultNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+}
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  4. Changed6 schema fields changed
    • 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"
+}
  5. Changed3 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • addedOutput schema / properties / data / properties / results
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "publicUrl": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / kind / enum
      Removed value: -[
-  "validation",
-  "business",
-  "platform",
-  "unknown"
-]
  6. 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"
+}
  7. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the connector/deep-research context and the types of results returned, but it does not disclose any additional behavioral traits such as matching behavior, pagination, or result limits. No contradiction exists.

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?

Two sentences, front-loaded with the tool's purpose and quickly routing to the alternative. There is no filler or redundant restatement of the schema.

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?

The tool is simple (one parameter), has an output schema, and has annotations covering the safety profile. The description covers purpose, result categories, and the sibling alternative; the only missing context is query semantics, which keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 for the single 'query' parameter. It implies the query is used to match artists, campaigns, and Smart Links, but it never explains what form the query should take, whether matching is fuzzy/exact, or whether it searches names or metadata. For a one-parameter tool this is a meaningful gap.

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: a search contract that returns matching Dynamoi artists, campaigns, and Smart Links for citation in deep-research sessions. It also explicitly distinguishes itself from the dynamoi_search sibling, making the tool's role unambiguous.

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 explicit when-to-use context ('OpenAI ChatGPT Deep Research / Connectors search') and names the alternative for a different scenario ('For regular ChatGPT chat use dynamoi_search instead'). This leaves no room for an agent to guess which tool to invoke.

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
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