Skip to main content
Glama
Sign In
MCP Documentation Service

MCP Documentation Service

by alekspetrov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

rename_document

Change a document's name while keeping its content and location intact. Optionally updates references to the renamed document in other files for consistency.

Instructions

Rename a document while preserving its location and content. Optionally updates references to the document in other files.

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": {
      "path": "<path>",
      "newName": "<newName>"
    },
    "name": "rename_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
newNameYes
updateReferencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions that the tool renames a document while preserving location and content, and optionally updates references, which gives some behavioral context. However, it lacks details on permissions needed, error conditions, whether the rename is atomic or reversible, or what happens if references fail to update, which are important for a mutation tool.

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?

The description is appropriately sized and front-loaded, with two clear sentences that efficiently convey the tool's purpose and optional behavior. Every sentence adds value without redundancy, making it easy for an agent to parse quickly.

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?

Given the tool has 3 parameters with 0% schema coverage, no annotations, and no output schema, the description provides basic context but is incomplete. It covers the main action and optional reference updating, but lacks details on return values, error handling, or advanced usage scenarios, which are needed for full agent understanding.

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 0%, so the description must compensate. It adds meaning by explaining that 'path' and 'newName' are used to rename the document, and 'updateReferences' controls whether references in other files are updated. However, it does not specify format for 'path' (e.g., file path syntax) or 'newName' (e.g., naming constraints), leaving gaps in parameter understanding.

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?

The description clearly states the tool's purpose with specific verbs ('rename', 'preserving', 'updates') and resource ('document'), distinguishing it from siblings like move_document (changes location) and edit_document (changes content). It explicitly mentions what is preserved (location and content) and what can be optionally updated (references).

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?

The description implies usage by mentioning 'preserving its location and content', suggesting this tool is for renaming without moving or modifying content, unlike move_document or edit_document. However, it does not explicitly state when to use this tool versus alternatives or provide exclusions, leaving some ambiguity for the agent.

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