Skip to main content
Glama
zhixuli0406

DuDuClaw

by zhixuli0406
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

wiki_share

Destructive

Publish a summary from your local wiki page to the shared wiki at sources/--.md with attribution; secret-scanned, and re-sharing overwrites the shared file.

Instructions

Publish a summary of one of your wiki pages to the shared wiki at sources/--.md with attribution; re-sharing overwrites it. Secret-scanned. Full shared pages: wiki_write scope=shared.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNoText to publish (default: first 500 characters of the page body)
page_pathYesPage path in your own wiki, relative to wiki/ (e.g. 'concepts/return-policy.md')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.74.0
    • changedInput schema / properties / page_path / description
      Previous value: -"Page path in your own wiki to share"New value: +"Page path in your own wiki, relative to wiki/ (e.g. 'concepts/return-policy.md')"
    • changedInput schema / properties / summary / description
      Previous value: -"Optional custom summary (default: first 500 chars of body)"New value: +"Text to publish (default: first 500 characters of the page body)"
  2. First observedv1.73.3

TDQS

A4.2/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: re-sharing overwrites the existing file (explaining the destructiveHint=true), content is secret-scanned, and attribution is added. These are meaningful operational facts an agent cannot infer from readOnlyHint=false/destructiveHint=true alone.

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 terse clauses, front-loaded with the action and destination; no filler. Every clause carries distinct information (destination, overwrite, scan, alternative).

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

Completeness4/5

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

For a publish tool with no output schema, the description covers destination, overwrite semantics, the secret scan, and the full-page alternative. Minor gaps remain (e.g., whether the published page is editable/removable afterward), but nothing critical for correct invocation 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%, so both parameters are already documented (including the summary default of the first 500 characters). The description adds only the destination filename pattern, so baseline 3 is appropriate.

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 (Publish) and resource (a summary of one of your wiki pages), plus the exact destination path template sources/<you>--<name>.md. It is clearly distinguishable from the sibling wiki_write, which handles full pages.

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

Usage Guidelines4/5

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

Explicitly routes the agent: this tool publishes a summary, while full shared pages should use wiki_write scope=shared. That names the alternative and the condition that selects it, though it does not spell out when-not to share at all.

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