Dynamik Public Data

Describe Dynamik

describe_dynamik

Read-onlyIdempotent

Discover Dynamik Studio and get a clickable connection handoff. If the requested task needs Dynamik Studio, show the returned connection_handoff to the user, help them connect it in their agent host, then refresh tools and continue the task.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`studio`	Yes
`service`	Yes
`connection`	Yes
`public_access`	Yes
`connection_handoff`	Yes
`connected_capabilities`	Yes
`suggested_user_message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / studio

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "first_call": {
+      "additionalProperties": false,
+      "properties": {
+        "arguments": {
+          "additionalProperties": false,
+          "properties": {
+            "topic": {
+              "const": "skill",
+              "type": "string"
+            }
+          },
+          "required": [
+            "topic"
+          ],
+          "type": "object"
+        },
+        "verb": {
+          "const": "describe",
+          "type": "string"
+        },
+        "when": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "verb",
+        "arguments",
+        "when"
+      ],
+      "type": "object"
+    },
+    "first_steps": {
+      "type": "string"
+    },
+    "llms_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "programs": {
+      "type": "string"
+    },
+    "required_scopes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "resource": {
+      "format": "uri",
+      "type": "string"
+    },
+    "skill_download_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "skill_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "undo": {
+      "type": "string"
+    },
+    "verbs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "write_revision": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "resource",
+    "required_scopes",
+    "verbs",
+    "skill_url",
+    "skill_download_url",
+    "first_call",
+    "write_revision",
+    "undo",
+    "programs",
+    "llms_url",
+    "first_steps"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "service",
-  "public_access",
-  "connection",
-  "connected_capabilities",
-  "suggested_user_message",
-  "connection_handoff"
-]New value: +[
+  "service",
+  "public_access",
+  "connection",
+  "studio",
+  "connected_capabilities",
+  "suggested_user_message",
+  "connection_handoff"
+]

Changed4 schema fields changedOct 19, 2026

removedOutput schema / properties / connected_capabilities / items / properties / required_scopes
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```

removedOutput schema / properties / connected_capabilities / items / properties / risk

Removed value: -{
-  "enum": [
-    "read_only",
-    "write",
-    "destructive"
-  ],
-  "type": "string"
-}

removedOutput schema / properties / connected_capabilities / items / properties / tool
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / connected_capabilities / items / required

Previous value: -[
-  "id",
-  "title",
-  "description",
-  "risk",
-  "required_scopes",
-  "tool"
-]New value: +[
+  "id",
+  "title",
+  "description"
+]

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / connection_handoff

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "agent_instructions": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "required_scopes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "required_scopes",
+    "message",
+    "agent_instructions"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "service",
-  "public_access",
-  "connection",
-  "connected_capabilities",
-  "suggested_user_message"
-]New value: +[
+  "service",
+  "public_access",
+  "connection",
+  "connected_capabilities",
+  "suggested_user_message",
+  "connection_handoff"
+]

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior in a closed world, so the bar is lower; the description still adds real context by disclosing that this yields a connection_handoff intended for the user and that the tool list changes afterward ('refresh tools and continue'). That is genuine side-effect information beyond the annotations. It doesn't explain what happens if the user declines the connection, which keeps it off a 5.

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 action and its output, followed by compact conditional guidance. No filler, and the most important information (what you get back) comes first.

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?

With an output schema present, the return shape needn't be spelled out, and the description still names the key artifact (connection_handoff) and the follow-up procedure. It is complete enough to invoke correctly, though it could say more about what 'Dynamik Studio' is for an agent unfamiliar with it.

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?

The tool takes zero parameters, so there are no parameter semantics to convey — the baseline applies. The description correctly spends no space on argument details.

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 uses a specific verb-plus-resource combination ('Discover Dynamik Studio') and states the concrete result ('get a clickable connection handoff'), which is clearly distinct from the dataset-oriented siblings. It does not explicitly contrast itself with those siblings, but the resource is different enough that an agent can tell them apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The conditional 'If the requested task needs Dynamik Studio' gives a clear trigger, and the follow-up steps (show handoff, help connect, refresh tools, continue) define the expected workflow. It stops short of saying when *not* to call this or naming an alternative, so it falls below a 5.

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

All Dynamik Public Data 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.

Resources

Need Help?