Skip to main content
Glama

move_document

DestructiveIdempotent

Mueve un documento a un nuevo padre (o a la raíz si new_parent_document_id es null)

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>"
    },
    "name": "move_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesID del documento a mover
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
new_parent_document_idNoID del nuevo padre; null para mover a raíz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered externally. The description adds no extra context: it doesn't warn about moving a document beneath its own descendant, what happens to child documents, or what permission is required for a destructive move.

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 zero padding that puts the operation and its edge case in one clause. Nothing could be cut, though the parenthetical adds no information not already in the schema.

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 3-parameter tool with full schema coverage and populated annotations, the definition is minimally viable. It falls short on the destructive and potentially cycle-inducing nature of a move, which is exactly the kind of thing an agent cannot derive from the structured fields alone.

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 parameter is documented in the schema, so the baseline is 3. The description's only parameter content (null means move to the root) restates the schema's own description of new_parent_document_id rather than adding format or validation detail.

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?

States a specific verb and resource ('Mueve un documento') plus the key state change: relocating it under a new parent, or to the root when the parent is null. It's clear what the tool does, but it never distinguishes itself from siblings like update_document or copy_document, which an agent must infer on its own.

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

Usage Guidelines2/5

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

No guidance on when to prefer this over alternatives such as update_document (which might also change the parent) or copy_document. The only conditional offered is the null-parent root case, which is a parameter behavior rather than a when-to-use rule; there are no prerequisites or exclusions.

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