Skip to main content
Glama
Sign In
RAGDown

RAGDown

by cubicecho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move or rename a document or subfolder

ragdown_move

Rename or move a document or subfolder inside the documents folder and rewrite all wikilinks and relative Markdown links to the new path. It never overwrites existing targets.

Instructions

Rename or move a document, or a subfolder with everything in it, to a new path inside the documents folder. Every link that pointed at what moved ([[wikilinks]] and relative Markdown links, in any document) is rewritten to still point at it, and the result names the documents that were updated. Never overwrites: if something is already at to, nothing moves. Use this rather than ragdown_write plus a delete, which would break the links.

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

Input Schema

NameRequiredDescriptionDefault
toYesIts whole new path, name included: 'db/postgres.md', not 'db/'. Missing subfolders on the way are created. A document keeps a Markdown extension
fromYesPath of the document or subfolder relative to the documents root, e.g. 'ops/pg.md' or 'ops'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.16.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only tell the agent it is not read-only, not destructive, and closed-world; the description adds substantive behavior beyond that: wikilink and relative Markdown links across any document are rewritten, nothing is overwritten on collision, and the result names the updated documents. These are the side effects an agent must know before calling a move 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?

Three sentences, front-loaded with what moves and where, then the link-rewrite consequence, then the alternative. No filler and every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by stating what the result contains ('names the documents that were updated'), and it covers the collision case and the link side effects. Nothing needed to invoke it correctly is missing.

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%, and both params already document their path format, extension rules, and subfolder creation in the schema. The description adds only the destination-scoping phrase and the no-overwrite rule, which is baseline for a fully documented two-parameter schema.

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 precise verb pair (rename/move) and resource (document or subfolder with its contents) and scopes the destination ('to a new path inside the documents folder'). It also explicitly contrasts itself with the naive ragdown_write + delete approach, so an agent can distinguish it from siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use and a named alternative with the reason it is wrong: 'Use this rather than ragdown_write plus a delete, which would break the links.' It also states the no-overwrite precondition, which tells the agent what to expect when a destination already exists.

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