Skip to main content
Glama

rename_document_file

DestructiveIdempotent

Renombra un archivo del workspace

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": {
      "file_id": "<file_id>",
      "new_name": "<new_name>"
    },
    "name": "rename_document_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesID del archivo
new_nameYesNuevo nombre del archivo (con extensión)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations establish that this is a non-read-only, destructive, idempotent operation, and the description does not contradict them. Beyond stating that a rename occurs, it adds no behavioral context about name collisions, overwriting, extension changes, permissions, or side effects.

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?

The single Spanish sentence is direct, front-loaded, and free of filler. Its brevity is clear, although it leaves little room for helpful selection or behavioral guidance.

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 simple three-parameter rename operation, the clear purpose, fully documented schema, and safety annotations make the definition minimally adequate. Important operational details and sibling differentiation remain absent, and there is no output schema to compensate for the lack of result information.

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%, including the required file identifier, the new name with extension, and when to omit workspace_id. The description adds no parameter meaning beyond that complete schema, so the baseline score 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?

"Renombra un archivo del workspace" clearly states the verb, resource, and workspace scope. It does not explicitly distinguish the operation from siblings such as move_document, copy_document, or update_document.

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?

The description implies use for renaming a workspace file, but provides no explicit when-to-use or when-not-to-use guidance. It does not identify prerequisites or route the agent to another tool for moves, copies, or content updates.

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