Skip to main content
Glama

copy_document

Copia un documento (nombre y contenido, sin sus hijos) a otro workspace —o al mismo—, en el servidor: el contenido no pasa por el modelo. Usar cuando el mismo documento tiene que estar en dos workspaces: crear uno y copiarlo, en vez de generarlo dos veces. Las imágenes siguen apuntando a los archivos del workspace de origen.

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": {
      "document_id": "<document_id>",
      "destino_workspace_id": "<destino_workspace_id>"
    },
    "name": "copy_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNombre de la copia (default: el mismo)
document_idYesID del documento a copiar
workspace_idNoUUID del workspace de ORIGEN
destino_workspace_idYesUUID o nombre del workspace de destino
destino_parent_document_idNoDocumento padre en el destino (omitir = raíz)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false; the description adds genuinely new behavioral facts —the copy runs server-side so content never passes through the model, children are not copied, and image references still point at the origin workspace's files. It is consistent with the annotations rather than contradicting them. It does not cover permission requirements or whether repeats create duplicate copies, which is why it is not a 5.

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?

Three short sentences: what it does and its scope first, when to use it second, and the one surprising side effect about images third. No repetition of the title or schema, nothing padding.

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 a 5-parameter server-side copy with no output schema, the description covers the essential operational facts: scope of the copy, the server-side execution model, and the image caveat. What is missing is the return value (e.g. the new document's ID or location) and any prerequisite about the destination workspace.

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 coverage is 100%, so the baseline is 3, and the description adds meaning on top by clarifying that the copy lands in another or the same workspace and that only name and content carry over —implying destino_parent_document_id places the copy under a parent. It does not clarify the optional origin workspace_id or the interaction between name and the existing title.

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 and resource ("Copia un documento ... a otro workspace —o al mismo—") and scopes exactly what is copied: name and content but not children. That scope detail distinguishes it from create_document and append_document without opening either schema.

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 an explicit decision rule: use it when the same document must exist in two workspaces, creating one and copying rather than generating twice. It does not name a sibling tool to avoid or state what happens if the destination already contains a copy.

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