Skip to main content
Glama

Duplicate Agent

duplicateAgent

Duplicate an existing agent into a new agent named "Copy of ", carrying over its configuration. Use the include_* flags in the (optional) body to control what is copied; all default on except memory. Builders can duplicate agents they created; duplicating an agent somebody else created requires the Lead Builder team role or above.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "duplicateAgent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe ID of the agent to duplicate
include_aopNoCopy the agent's operating procedure (AOP) and its handover targets. Defaults to true.
include_queueNoCopy the assigned Queue. Defaults to true.
include_memoryNoCopy what the agent has learned so far (its Memory). Defaults to false. Memory can only be copied from the Duvo app — requesting it here returns an error.
include_pluginsNoCopy installed plugins. Defaults to true.
include_connectionsNoCopy connected accounts (Connections) and their selected tools. Defaults to true.
include_skills_filesNoCopy attached Skills and Files. Defaults to true.
include_logins_secretsNoCopy saved Logins and Secrets. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond annotations: a permission model, the default-on-except-memory policy, and the notable failure mode that include_memory returns an error outside the Duvo app. It stops short of describing the return value or whether repeated calls produce multiple copies, but the annotations already flag non-idempotency.

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 tightly written sentences, front-loaded with the core action and outcome, then the flag policy and permission qualifier. No filler.

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?

For an 8-parameter mutation tool with no output schema, this covers outcome naming, flag defaults, permissions, and the memory error case. Only the response shape and any side effects on the source agent are unaddressed.

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 coverage is 100% and every flag already documents its own default and meaning, so the description's "all default on except memory" summary is largely restated information. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb (duplicate) and resource (agent), plus the concrete outcome: a new agent named "Copy of <name>" carrying over configuration. That naming detail alone distinguishes it from createAgent or getAgent siblings.

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?

Gives clear permission context: builders can duplicate their own agents, duplicating someone else's requires Lead Builder team role or above. It also tells the agent to use include_* flags to control scope, though it never explicitly contrasts with createAgent for building from scratch.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources