Skip to main content
Glama

clone_agent

Duplicate an existing agent with its schemas and optionally its triggers to create a new agent. Cloned triggers start disabled for review before enabling.

Instructions

Clone agent with schemas and optionally triggers

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": "clone_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesUUID of the agent to clone
new_nameNoClone name; omit to use the generated name
include_schemasNoClone the agent schemas
include_triggersNoClone triggers; cloned triggers are initially disabled

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.4
    • changedInput schema / properties / agent_id / description
      Previous value: -"UUID do agente a clonar"New value: +"UUID of the agent to clone"
    • changedInput schema / properties / include_schemas / description
      Previous value: -"Clonar schemas do agente"New value: +"Clone the agent schemas"
    • changedInput schema / properties / include_triggers / description
      Previous value: -"Clonar triggers (serão criados desabilitados)"New value: +"Clone triggers; cloned triggers are initially disabled"
    • changedInput schema / properties / new_name / description
      Previous value: -"Nome do clone (default: \"Cópia de <original>\")"New value: +"Clone name; omit to use the generated name"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds that clone output includes schemas and that cloned triggers start disabled (a useful behavioral note), but that disabled-trigger detail is already repeated from the schema, and the description says nothing about creating a persistent new agent each call or what identity the clone receives.

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?

A single front-loaded sentence with no filler. It is efficient, though it is arguably too terse for a mutation tool that produces a new agent.

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?

For a four-parameter mutation tool with no output schema, the definition never says what is returned (e.g., a new agent ID) or how to reference the clone afterwards. Combined with the absence of alternative-tool guidance, an agent can technically call it but lacks orientation about the result.

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 all four parameters are fully documented in the schema, including defaults for include_schemas (true) and include_triggers (false). The description only paraphrases those fields and adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 states a specific verb ('clone') and resource ('agent'), plus scope qualifiers (schemas included, triggers optional). It is clear what the tool does, but it offers no differentiation from sibling tools such as create_agent.

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?

Usage is only implied: the agent must infer that this is for duplicating an existing agent rather than authoring a new one. There is no explicit when-to-use guidance, no mention of create_agent as the alternative for building from scratch, and no stated prerequisites.

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

Deploy Server

Other Tools