Skip to main content
Glama
Sign In
DuDuClaw

DuDuClaw

by zhixuli0406
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

wiki_search

Read-only

Full-text search of wiki pages, trust-weighted, with layer/min_trust filters and optional 1-hop expand. scope="shared" searches the shared wiki. Notes outside the wiki: memory_search.

Instructions

Full-text search of wiki pages, trust-weighted, with layer/min_trust filters and optional 1-hop expand. scope="shared" searches the shared wiki. Notes outside the wiki: memory_search.

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": {
      "query": "<query>"
    },
    "name": "wiki_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNoFilter by layer: identity/core/context/deep
limitNoMax results (default 10, max 100)
queryYesSearch query (keywords)
scopeNo"agent" (your own wiki, the default) or "shared" (the cross-agent knowledge base). Shared writes honour the namespace SoT policy — check wiki_namespace_status first.
expandNoAlso return pages one related/backlink hop away (default false). Ignored when scope="shared".
agent_idNoAgent name (default: main agent)
min_trustNoDrop pages whose trust is below this, 0.0 to 1.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.74.0
    • changedInput schema / properties / expand / description
      Previous value: -"1-hop expand via related/backlinks (true/false, default: false). Ignored when scope=\"shared\"."New value: +"Also return pages one related/backlink hop away (default false). Ignored when scope=\"shared\"."
    • changedInput schema / properties / expand / type
      Previous value: -"string"New value: +"boolean"
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default: 10)"New value: +"Max results (default 10, max 100)"
    • changedInput schema / properties / limit / type
      Previous value: -"string"New value: +"integer"
    • changedInput schema / properties / min_trust / description
      Previous value: -"Minimum trust score filter (0.0-1.0)"New value: +"Drop pages whose trust is below this, 0.0 to 1.0"
    • changedInput schema / properties / min_trust / type
      Previous value: -"string"New value: +"number"
  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?

Annotations already declare readOnlyHint and openWorldHint=false, but the description adds real behavioral detail beyond them: results are trust-weighted, and the expand hop is ignored when scope="shared". It does not discuss ranking order or result shape, which keeps it out of 5 territory.

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 tight clauses, front-loaded with the core action and followed immediately by the routing constraint. Every sentence earns its place, including the memory_search pointer.

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 7-parameter read-only search tool with no output schema, the description covers scope semantics, the expand caveat, filter availability, and the sibling routing. It is complete enough to select and invoke correctly, though it says nothing about result ordering or empty-result behavior.

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 coverage is 100% and each parameter already carries a rich description, so the schema does the heavy lifting. The description restates layer/min_trust/expand in passing and adds the shared-scope quirk, which is marginal added value over the 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 specific verb and resource ('Full-text search of wiki pages') plus its distinguishing traits: trust-weighted ranking, layer/min_trust filters, and optional 1-hop expand. It also separates itself from the memory_* siblings by noting that notes outside the wiki belong to memory_search.

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?

Names the alternative explicitly ('Notes outside the wiki: memory_search') and explains the scope="shared" routing condition. It stops short of an explicit when-not-to-use against wiki_ls/wiki_read, so it is strong but not exhaustive.

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