Skip to main content
Glama

Duvo MCP

by io.github.duvoai

Create Agent

createAgent

Create a new agent. Optionally include a build configuration to create the first build in the same request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable agent name
typeNoFlavour of the step to create. Fixed at creation — it selects the config family every build of this step must use, and the two cannot be mixed.agent
buildNoOptional inline build. When present, a first build is created alongside the agent. Only valid for an agent step.
team_idNoDuvo team UUID to operate on. API keys are pinned to a single team — omit this (it falls back to the key's team) or pass that same team; a different team is rejected. OAuth callers, who can span multiple teams, should pass the target team here.
thread_idNoExisting thread ID to associate with the agent
automation_idNoAutomation this agent belongs to. If omitted on a team using the automations model, a new automation named after the agent is created automatically.
source_build_idNoBuild ID whose case-queue-consumer setup should be copied to the new agent

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / build / properties / config / properties / data / properties / subAgents / description
      Previous value: -"IDs of other agents (in the same team) to expose to this agent as Claude Code subagents. Each sub-agent runs with its own AOP and connections; the parent can delegate to them via the Agent tool."New value: +"Retired — Sub-Assignments was removed. Accepted for backwards compatibility and ignored."
  2. Changed3 schema fields changed
    • changedInput schema / properties / build / description
      Previous value: -"Optional inline build. When present, a first build is created alongside the agent."New value: +"Optional inline build. When present, a first build is created alongside the agent. Only valid for an agent step."
    • changedInput schema / properties / build / properties / config / description
      Previous value: -"Build configuration (latest schema version only; legacy v1 configs are not accepted)"New value: +"Build configuration (latest schema version only; legacy v1 configs are not accepted). Agent steps only — a code step's first build is created via `POST /v2/agents/{agent_id}/revisions`, which accepts a code-step config."
    • addedInput schema / properties / type
      Added value: +{
+  "default": "agent",
+  "description": "Flavour of the step to create. Fixed at creation — it selects the config family every build of this step must use, and the two cannot be mixed.",
+  "enum": [
+    "agent",
+    "code"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / build / properties / config / properties / data / properties / models / properties / agent / properties / model / enum
      Previous value: -[
-  "claude-haiku-4-5-20251001",
-  "claude-sonnet-5",
-  "claude-sonnet-5[1m]",
-  "claude-opus-5",
-  "claude-opus-5[1m]",
-  "kimi-k3",
-  "kimi-k3-duvo",
-  "glm-5.2",
-  "deepseek-v4-flash",
-  "minimax-m3",
-  "qwen3.6-27b",
-  "d1-max",
-  "duvo-1-max",
-  "duvo-1-max-sonnet-1m",
-  "duvo-1-max-sonnet-4.5",
-  "duvo-1-max-sonnet-4.5-1m",
-  "duvo-1-max-opus",
-  "duvo-1-max-opus-4.5",
-  "gpt-4.1",
-  "gpt-4o",
-  "gpt-4o-mini",
-  "gpt-5",
-  "gpt-5.1",
-  "claude-sonnet-4-20250514",
-  "claude-sonnet-4-20250514[1m]",
-  "claude-sonnet-4-5-20250929",
-  "claude-sonnet-4-5-20250929[1m]",
-  "claude-sonnet-4-6",
-  "claude-sonnet-4-6[1m]",
-  "claude-opus-4-1-20250805",
-  "claude-opus-4-5-20251101",
-  "claude-opus-4-6",
-  "claude-opus-4-6[1m]",
-  "claude-opus-4-7",
-  "claude-opus-4-7[1m]",
-  "claude-opus-4-8",
-  "claude-opus-4-8[1m]"
-]New value: +[
+  "claude-haiku-4-5-20251001",
+  "claude-sonnet-5",
+  "claude-sonnet-5[1m]",
+  "claude-opus-5",
+  "claude-opus-5[1m]",
+  "kimi-k3",
+  "kimi-k3-duvo",
+  "glm-5.2",
+  "glm-5.3-flash",
+  "deepseek-v4-flash",
+  "minimax-m3",
+  "qwen3.6-27b",
+  "d1-max",
+  "duvo-1-max",
+  "duvo-1-max-sonnet-1m",
+  "duvo-1-max-sonnet-4.5",
+  "duvo-1-max-sonnet-4.5-1m",
+  "duvo-1-max-opus",
+  "duvo-1-max-opus-4.5",
+  "gpt-4.1",
+  "gpt-4o",
+  "gpt-4o-mini",
+  "gpt-5",
+  "gpt-5.1",
+  "claude-sonnet-4-20250514",
+  "claude-sonnet-4-20250514[1m]",
+  "claude-sonnet-4-5-20250929",
+  "claude-sonnet-4-5-20250929[1m]",
+  "claude-sonnet-4-6",
+  "claude-sonnet-4-6[1m]",
+  "claude-opus-4-1-20250805",
+  "claude-opus-4-5-20251101",
+  "claude-opus-4-6",
+  "claude-opus-4-6[1m]",
+  "claude-opus-4-7",
+  "claude-opus-4-7[1m]",
+  "claude-opus-4-8",
+  "claude-opus-4-8[1m]"
+]
    • changedInput schema / properties / build / properties / config / properties / data / properties / models / properties / agent / properties / model / x-extensible-enum
      Previous value: -[
-  "claude-haiku-4-5-20251001",
-  "claude-sonnet-5",
-  "claude-sonnet-5[1m]",
-  "claude-opus-5",
-  "claude-opus-5[1m]",
-  "kimi-k3",
-  "kimi-k3-duvo",
-  "glm-5.2",
-  "deepseek-v4-flash",
-  "minimax-m3",
-  "qwen3.6-27b",
-  "d1-max",
-  "duvo-1-max",
-  "duvo-1-max-sonnet-1m",
-  "duvo-1-max-sonnet-4.5",
-  "duvo-1-max-sonnet-4.5-1m",
-  "duvo-1-max-opus",
-  "duvo-1-max-opus-4.5",
-  "gpt-4.1",
-  "gpt-4o",
-  "gpt-4o-mini",
-  "gpt-5",
-  "gpt-5.1",
-  "claude-sonnet-4-20250514",
-  "claude-sonnet-4-20250514[1m]",
-  "claude-sonnet-4-5-20250929",
-  "claude-sonnet-4-5-20250929[1m]",
-  "claude-sonnet-4-6",
-  "claude-sonnet-4-6[1m]",
-  "claude-opus-4-1-20250805",
-  "claude-opus-4-5-20251101",
-  "claude-opus-4-6",
-  "claude-opus-4-6[1m]",
-  "claude-opus-4-7",
-  "claude-opus-4-7[1m]",
-  "claude-opus-4-8",
-  "claude-opus-4-8[1m]"
-]New value: +[
+  "claude-haiku-4-5-20251001",
+  "claude-sonnet-5",
+  "claude-sonnet-5[1m]",
+  "claude-opus-5",
+  "claude-opus-5[1m]",
+  "kimi-k3",
+  "kimi-k3-duvo",
+  "glm-5.2",
+  "glm-5.3-flash",
+  "deepseek-v4-flash",
+  "minimax-m3",
+  "qwen3.6-27b",
+  "d1-max",
+  "duvo-1-max",
+  "duvo-1-max-sonnet-1m",
+  "duvo-1-max-sonnet-4.5",
+  "duvo-1-max-sonnet-4.5-1m",
+  "duvo-1-max-opus",
+  "duvo-1-max-opus-4.5",
+  "gpt-4.1",
+  "gpt-4o",
+  "gpt-4o-mini",
+  "gpt-5",
+  "gpt-5.1",
+  "claude-sonnet-4-20250514",
+  "claude-sonnet-4-20250514[1m]",
+  "claude-sonnet-4-5-20250929",
+  "claude-sonnet-4-5-20250929[1m]",
+  "claude-sonnet-4-6",
+  "claude-sonnet-4-6[1m]",
+  "claude-opus-4-1-20250805",
+  "claude-opus-4-5-20251101",
+  "claude-opus-4-6",
+  "claude-opus-4-6[1m]",
+  "claude-opus-4-7",
+  "claude-opus-4-7[1m]",
+  "claude-opus-4-8",
+  "claude-opus-4-8[1m]"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / build / properties / config / properties / data / properties / files / description
      Previous value: -"IDs of team files that should be available to the agent"New value: +"Team files that should be available to the agent, each given as the relative file path returned in the `path` field of `GET /v2/teams/{teamId}/files` (for example `report.md` or `folder/doc.md`) — not the `id` field, which is a GCS object identifier."
  5. Changed2 schema fields changed
    • changedInput schema / properties / build / properties / config / properties / data / properties / models / properties / agent / properties / model / enum
      Previous value: -[
-  "claude-haiku-4-5-20251001",
-  "claude-sonnet-5",
-  "claude-sonnet-5[1m]",
-  "claude-opus-5",
-  "claude-opus-5[1m]",
-  "kimi-k3",
-  "glm-5.2",
-  "deepseek-v4-flash",
-  "minimax-m3",
-  "qwen3.6-27b",
-  "d1-max",
-  "duvo-1-max",
-  "duvo-1-max-sonnet-1m",
-  "duvo-1-max-sonnet-4.5",
-  "duvo-1-max-sonnet-4.5-1m",
-  "duvo-1-max-opus",
-  "duvo-1-max-opus-4.5",
-  "gpt-4.1",
-  "gpt-4o",
-  "gpt-4o-mini",
-  "gpt-5",
-  "gpt-5.1",
-  "claude-sonnet-4-20250514",
-  "claude-sonnet-4-20250514[1m]",
-  "claude-sonnet-4-5-20250929",
-  "claude-sonnet-4-5-20250929[1m]",
-  "claude-sonnet-4-6",
-  "claude-sonnet-4-6[1m]",
-  "claude-opus-4-1-20250805",
-  "claude-opus-4-5-20251101",
-  "claude-opus-4-6",
-  "claude-opus-4-6[1m]",
-  "claude-opus-4-7",
-  "claude-opus-4-7[1m]",
-  "claude-opus-4-8",
-  "claude-opus-4-8[1m]"
-]New value: +[
+  "claude-haiku-4-5-20251001",
+  "claude-sonnet-5",
+  "claude-sonnet-5[1m]",
+  "claude-opus-5",
+  "claude-opus-5[1m]",
+  "kimi-k3",
+  "kimi-k3-duvo",
+  "glm-5.2",
+  "deepseek-v4-flash",
+  "minimax-m3",
+  "qwen3.6-27b",
+  "d1-max",
+  "duvo-1-max",
+  "duvo-1-max-sonnet-1m",
+  "duvo-1-max-sonnet-4.5",
+  "duvo-1-max-sonnet-4.5-1m",
+  "duvo-1-max-opus",
+  "duvo-1-max-opus-4.5",
+  "gpt-4.1",
+  "gpt-4o",
+  "gpt-4o-mini",
+  "gpt-5",
+  "gpt-5.1",
+  "claude-sonnet-4-20250514",
+  "claude-sonnet-4-20250514[1m]",
+  "claude-sonnet-4-5-20250929",
+  "claude-sonnet-4-5-20250929[1m]",
+  "claude-sonnet-4-6",
+  "claude-sonnet-4-6[1m]",
+  "claude-opus-4-1-20250805",
+  "claude-opus-4-5-20251101",
+  "claude-opus-4-6",
+  "claude-opus-4-6[1m]",
+  "claude-opus-4-7",
+  "claude-opus-4-7[1m]",
+  "claude-opus-4-8",
+  "claude-opus-4-8[1m]"
+]
    • changedInput schema / properties / build / properties / config / properties / data / properties / models / properties / agent / properties / model / x-extensible-enum
      Previous value: -[
-  "claude-haiku-4-5-20251001",
-  "claude-sonnet-5",
-  "claude-sonnet-5[1m]",
-  "claude-opus-5",
-  "claude-opus-5[1m]",
-  "kimi-k3",
-  "glm-5.2",
-  "deepseek-v4-flash",
-  "minimax-m3",
-  "qwen3.6-27b",
-  "d1-max",
-  "duvo-1-max",
-  "duvo-1-max-sonnet-1m",
-  "duvo-1-max-sonnet-4.5",
-  "duvo-1-max-sonnet-4.5-1m",
-  "duvo-1-max-opus",
-  "duvo-1-max-opus-4.5",
-  "gpt-4.1",
-  "gpt-4o",
-  "gpt-4o-mini",
-  "gpt-5",
-  "gpt-5.1",
-  "claude-sonnet-4-20250514",
-  "claude-sonnet-4-20250514[1m]",
-  "claude-sonnet-4-5-20250929",
-  "claude-sonnet-4-5-20250929[1m]",
-  "claude-sonnet-4-6",
-  "claude-sonnet-4-6[1m]",
-  "claude-opus-4-1-20250805",
-  "claude-opus-4-5-20251101",
-  "claude-opus-4-6",
-  "claude-opus-4-6[1m]",
-  "claude-opus-4-7",
-  "claude-opus-4-7[1m]",
-  "claude-opus-4-8",
-  "claude-opus-4-8[1m]"
-]New value: +[
+  "claude-haiku-4-5-20251001",
+  "claude-sonnet-5",
+  "claude-sonnet-5[1m]",
+  "claude-opus-5",
+  "claude-opus-5[1m]",
+  "kimi-k3",
+  "kimi-k3-duvo",
+  "glm-5.2",
+  "deepseek-v4-flash",
+  "minimax-m3",
+  "qwen3.6-27b",
+  "d1-max",
+  "duvo-1-max",
+  "duvo-1-max-sonnet-1m",
+  "duvo-1-max-sonnet-4.5",
+  "duvo-1-max-sonnet-4.5-1m",
+  "duvo-1-max-opus",
+  "duvo-1-max-opus-4.5",
+  "gpt-4.1",
+  "gpt-4o",
+  "gpt-4o-mini",
+  "gpt-5",
+  "gpt-5.1",
+  "claude-sonnet-4-20250514",
+  "claude-sonnet-4-20250514[1m]",
+  "claude-sonnet-4-5-20250929",
+  "claude-sonnet-4-5-20250929[1m]",
+  "claude-sonnet-4-6",
+  "claude-sonnet-4-6[1m]",
+  "claude-opus-4-1-20250805",
+  "claude-opus-4-5-20251101",
+  "claude-opus-4-6",
+  "claude-opus-4-6[1m]",
+  "claude-opus-4-7",
+  "claude-opus-4-7[1m]",
+  "claude-opus-4-8",
+  "claude-opus-4-8[1m]"
+]
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already signal a mutating, non-idempotent operation (readOnlyHint=false, idempotentHint=false), and 'Create' is fully consistent with them — no contradiction. The description adds one genuine side-effect disclosure: passing a build creates the first build in the same request. Other behavioral traits, such as automation_id's note that an automation is auto-created when omitted and type being fixed at creation, live in the schema rather than the description, leaving the description itself thin on behavior.

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 totaling roughly twenty words, with the core purpose front-loaded in sentence one and the optional capability in sentence two. There is no filler, no repetition of the title or schema, and every word earns its place. This is a model of compact description writing.

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?

Despite high complexity — 7 parameters with deeply nested build/config/data objects — the schema comprehensively documents every level, including side effects and alternative routes (code-step builds routed to revisions, team_id key-pinning rules for API vs OAuth callers). The main description is brief, but the definition as a whole equips an agent to select and invoke the tool correctly. The absence of an output schema and any hint of what the create response returns keeps this from a 5.

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 100%, so the baseline of 3 applies, and the schema is unusually rich: files distinguishes path from GCS id, agent model conditions on the team's oss_models flag, plugins distinguishes built-ins from GitHub URLs, and subAgents documents its own retirement. The main description contributes only marginal parameter context ('Optionally include a build configuration'), which merely echoes the schema's own detailed build documentation. The schema carries the load here.

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 opens with 'Create a new agent,' a specific verb+resource that clearly matches the tool name and sets it apart from narrow siblings like createAgentCaseTrigger, createAgentFolder, and createAgentSlackTrigger. The second sentence adds real scope detail (optional inline build), clarifying this is the full agent-creation entry point. It stops short of a 5 because it never explicitly names what it is not, such as duplicateAgent or the code-step revision path.

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

Usage Guidelines3/5

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

The top-level description only implies when to use the tool (whenever a new agent is needed) and gives no explicit alternatives or exclusions. The strongest guidance is embedded in the schema: the build.config description explicitly says code steps' first builds must go through POST /v2/agents/{agent_id}/revisions, and the type description warns the step flavor is fixed at creation. There is no routing guidance against related tools like updateAgent or duplicateAgent, so guidance is partial rather than complete.

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

B3.1/5.0
Disambiguation2/5

Despite detailed descriptions, many tool names are highly ambiguous, with multiple tools covering the same conceptual actions (e.g., acceptClarityCaptureSuggestion vs. acceptClarityTeamAssignmentSuggestion, or the many deleteClarity*Interview tools). The set is so large that distinguishing between, say, listClarityFolders, listClarityProcesses, and listClarityProcessSummaries requires reading deep into descriptions, reducing agent selection accuracy.

Naming Consistency4/5

The naming convention is predominantly verb_noun (e.g., createClarityProcess, listAgents, deleteQueue), and is remarkably consistent across the 316 tools. There are only minor deviations, such as 'fileSuggestedClarityProcesses' (verb + adjective noun) and 'bulkUpdateCasePriority' (where 'bulk' could be seen as a prefix), but overall the pattern holds strongly.

Tool Count1/5

With 316 tools, this server is extremely oversized for any single agent to manage effectively. The massive number of tools suggests poor modularization—many of these tools likely belong in separate, smaller servers focused on specific domains (e.g., Clarity, Pulse, Agent management). The cognitive load for an agent to choose from 316 options is very high, leading to frequent misselection.

Completeness4/5

The tool surface covers an extraordinarily wide range of operations across the Duvo platform: agents, runs, cases, queues, Clarity processes, skills, integrations, notifications, teams, and more. Most resource types have full CRUD and lifecycle management. Notable minor gaps exist (e.g., no tools for managing specific notification batch severities dynamically, and some interview management is missing batch operations), but for the platform's scope, coverage is impressively thorough.

Resources