Skip to main content
Glama

Duvo MCP

by io.github.duvoai
OverviewDiscussionsAdmin

Send Pulse Dashboard Message

sendPulseDashboardMessage

Send an instruction to iterate on a Duvo Pulse dashboard (e.g. 'make it a bar chart', 'filter to last 14 days'). The creator can always iterate; teammates can too when the Pulse is published to the team with edit access. The agent regenerates asynchronously — poll GET /artifacts/{artifactId} for status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes
artifactIdYes
attachmentsNoAttachments to hand the agent, uploaded beforehand via the upload-urls endpoint (max 5)
from_revision_idNo
selected_elementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / selected_element / properties / point
      Added value: +{
+  "properties": {
+    "x_ratio": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    },
+    "y_ratio": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "x_ratio",
+    "y_ratio"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / selected_element / properties / openui_node
      Added value: +{
+  "properties": {
+    "component": {
+      "maxLength": 100,
+      "minLength": 1,
+      "type": "string"
+    },
+    "source": {
+      "maxLength": 2000,
+      "type": "string"
+    },
+    "statement": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "statement",
+    "component"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses that the tool triggers asynchronous regeneration and instructs polling the artifact status, which is key behavioral information not fully captured by annotations. It aligns with annotations (readOnlyHint false, destructiveHint false) and adds operational detail.

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 description is concise and well-structured, using three sentences to convey purpose, permissions, and async behavior. Minor awkwardness like 'Duvo Pulse' (possibly a typo) slightly detracts, but overall it is efficient.

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

Completeness3/5

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

The description covers the core action and async polling, but given the complexity of five parameters and nested objects, it leaves out important context about attachments and revision handling. It does not describe the expected outcome or response format, though the polling URL partially compensates.

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?

With only 20% schema description coverage, the description provides minimal help for parameters. It indirectly mentions the message and artifactId via examples and the polling URL, but attachments, from_revision_id, and nested objects are left unexplained, leaving the agent to guess.

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 clearly states that the tool sends an instruction to iterate on a Pulse dashboard, with concrete examples of such instructions. It distinguishes the tool's purpose from other dashboard-related actions, making it easy for an agent to understand when to use it.

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 description provides usage context by explaining who can iterate (creator always, teammates with edit access when published) and that the operation is asynchronous, requiring polling. It does not explicitly compare to alternative tools, but the conditions and workflow are sufficiently clear.

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

All Duvo MCP 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