Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

clone_cell

Duplicates a block with all its contentBlocks (and kindMetadata for arch/process/journey/captable, and the fields/source for entity/data-source) under a new parent. Structural dependency auto-created only for blocks with kind='org'. The children and assignments are NOT cloned. The link to a linked project (projectLink) is NOT copied either — a project link stays an explicit action (link_project_to_cell), and not a side effect of cloning. A child is cloned by its own clone_cell call.

Input Schema

NameRequiredDescriptionDefault
newIdYesUnique ID for the new block
newNameNoNew name (default: `Copie de {name}`, in French)
sourceIdYesID of the block to duplicate
newParentIdNoID of the parent for the copy (default: same parent as the source)
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.
confirmRootPlacementNo⚠️ Required (true) ONLY if the project has locked its root placement (Settings) AND the clone is born WITHOUT a parent (newParentId omitted with a root source, or newParentId explicitly null): without it, the creation of this NEW root is refused. Not applicable if the root placement is not locked, or if an actual newParentId applies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / confirmRootPlacement / description
      Previous value: -"⚠️ Requis (true) UNIQUEMENT si le projet a verrouillé son placement racine (Réglages) ET que le clone naît SANS parent (newParentId omis avec une source racine, ou newParentId explicitement null) : sans lui, la création de cette NOUVELLE racine est refusée. Sans objet si le placement racine n'est pas verrouillé, ou si un newParentId réel s'applique."New value: +"⚠️ Required (true) ONLY if the project has locked its root placement (Settings) AND the clone is born WITHOUT a parent (newParentId omitted with a root source, or newParentId explicitly null): without it, the creation of this NEW root is refused. Not applicable if the root placement is not locked, or if an actual newParentId applies."
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
    • changedInput schema / properties / newId / description
      Previous value: -"ID unique pour la nouvelle cellule"New value: +"Unique ID for the new block"
    • changedInput schema / properties / newName / description
      Previous value: -"Nouveau nom (défaut: 'Copie de {nom}')"New value: +"New name (default: `Copie de {name}`, in French)"
    • changedInput schema / properties / newParentId / description
      Previous value: -"ID du parent pour la copie (défaut: même parent que source)"New value: +"ID of the parent for the copy (default: same parent as the source)"
    • changedInput schema / properties / sourceId / description
      Previous value: -"ID de la cellule à dupliquer"New value: +"ID of the block to duplicate"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare non-read-only, non-destructive, closed-world) by disclosing side effects and refusal conditions: a structural dependency is auto-created only for kind='org', and root placement may be refused without confirmRootPlacement. These are exactly the mutation side effects an agent needs.

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?

Front-loads what is cloned before the exceptions, and each sentence covers a distinct cloning rule that earns its place. It is dense and slightly long, but not padded.

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 no output schema, the description covers the important behavioral contract (what is copied, what isn't, refusal cases) thoroughly. It does not describe the return value of the clone, a minor gap for a tool with no output schema.

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?

Schema description coverage is 100%, so the baseline is 3; the description reinforces and adds rationale for the newParentId/confirmRootPlacement interaction and the expectedProjectId refusal behavior. It adds contextual meaning about cloning rules, though little new syntax beyond the schema.

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 (duplicates) and resource (a block with all its contentBlocks), scoping precisely what is and isn't copied. It also names the sibling it is distinct from (link_project_to_cell), so an agent can differentiate it without opening any schema.

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

Usage Guidelines5/5

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

Explicitly says what is NOT cloned (children, assignments, projectLink), directs project linking to the alternative tool link_project_to_cell, and explains that a child is cloned via its own clone_cell call. This gives clear when/when-not conditions and the alternative.

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

All OrgGen AI 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