Skip to main content
Glama
Sign In
DuDuClaw

DuDuClaw

by zhixuli0406
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

wiki_export

DestructiveIdempotent

Export your DuDuClaw wiki to /exports as a single HTML file or Obsidian vault, returning the path and overwriting only previous exports.

Instructions

Export a wiki (yours by default) under /exports as one HTML file (default) or an Obsidian vault folder; returns the path. Overwrites the previous export, never the wiki itself.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wiki_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo'html' (default, one file) or 'obsidian' (a folder of .md files with wikilinks)
agent_idNoAgent name (default: main agent)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.74.0
    • changedInput schema / properties / format / description
      Previous value: -"Export format: 'obsidian' or 'html' (default: html)"New value: +"'html' (default, one file) or 'obsidian' (a folder of .md files with wikilinks)"
  2. First observedv1.73.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description meaningfully scopes that destructiveness: it explains that the previous export is overwritten while the wiki itself is never touched, which is precisely the risk an agent needs bounded. It also discloses the return value ('returns the path'). It stops short of covering permissions or failure modes, but it adds real context beyond the annotations.

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?

Two compact sentences, front-loaded with the action and destination, followed by the safety-critical caveat. Every clause earns its place and nothing is repeated.

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?

For a two-parameter, no-required-params tool with no output schema, the description covers destination, format options, defaults, return value, and the destructive side effect. Nothing an agent needs in order to invoke this 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 parameters are fully documented in the schema (format's html/obsidian meanings, agent_id's default). The description restates the same defaults ('yours by default', 'one HTML file (default)') without adding syntax or behavior not already in the schema, so the baseline of 3 applies.

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 specific verb and resource ('Export a wiki'), names the output location (<home>/exports), both output formats with defaults, and the return value. There is no sibling export tool to confuse it with, so no differentiation is needed, and none of the sibling read/write/lint tools could be mistaken for this.

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?

Usage is implied rather than stated: 'yours by default' signals the agent_id parameter lets you target another agent's wiki, and the format defaults are given. However, there is no explicit when-to-use guidance, no mention of prerequisites, and no note on when the Obsidian versus HTML format should be chosen beyond the raw format descriptions.

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