Skip to main content
Glama

write_rename_asset

Renames a file attached to a LeafWiki page by specifying the page identifier, current filename, and new filename.

Instructions

Rename a file attached to a page.

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": {
      "page": "<page>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "write_rename_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
pageYesPage id or path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations only declare openWorldHint=false and destructiveHint=false; the description adds nothing about what a rename does to existing references, whether it fails when the source name is absent, or whether the target name collides. For a mutation tool, this leaves behavior largely undisclosed beyond the safety hints.

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 no filler or redundancy. Its brevity is clean, though the terseness comes at the cost of the details captured in the other dimensions.

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 three-required-parameter mutation with no output schema and only partial schema descriptions, the definition is thin: the two filename parameters and the failure modes of renaming go unexplained. It is minimally adequate to identify the operation but not to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 33% — only `page` is documented ("Page id or path"). The description does not explain `from` and `to` at all, not even that they are the old and new file names, nor does it mention the restriction that `to` cannot contain slashes.

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 (rename) and a specific resource (a file attached to a page), which usefully distinguishes it from page-level operations like write_move or write_edit_text. It does not, however, name or contrast with the closest siblings such as write_upload_asset or delete_asset.

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 contains no when-to-use guidance, no prerequisites (e.g., that the file must already be attached and the old name must exist), and no mention of alternatives for moving or replacing assets. The agent must infer usage entirely.

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