Skip to main content
Glama
Sign In
DuDuClaw

DuDuClaw

by zhixuli0406
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

wiki_graph

Read-only

Render a wiki link graph as a Mermaid diagram, or focus on pages within a set number of hops from a center page for read-only visualization.

Instructions

Render the wiki link graph as a Mermaid diagram (nodes = pages, edges = related links), or only pages within depth hops of center. Read-only.

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_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoMax hops from center (default 2, capped at 10; ignored without center)
centerNoCenter page path for focused view (e.g. 'entities/customer.md')
agent_idNoAgent name (default: main agent)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.74.0
    • changedInput schema / properties / depth / description
      Previous value: -"Max hops from center (default: 2, ignored without center)"New value: +"Max hops from center (default 2, capped at 10; ignored without center)"
    • changedInput schema / properties / depth / type
      Previous value: -"string"New value: +"integer"
  2. First observedv1.73.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description redundantly restates 'Read-only,' which earns no credit. However, with no output schema, describing the return as a Mermaid diagram with nodes=pages and edges=related links is genuinely valuable behavioral context the annotations do not supply.

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?

A single front-loaded sentence that conveys purpose, output format, the optional focused mode, and the read-only nature with no wasted words.

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 read-only render tool with no output schema and fully documented parameters, the description covers purpose, output shape, and the optional narrowing mode adequately. It stops short of describing diagram size limits or a concrete output sample, a minor gap.

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 all three parameters (depth, center, agent_id) are already documented in the schema with defaults, caps, and the 'ignored without center' caveat. The description only lightly restates the depth/center relationship, adding no syntax or format detail beyond 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 (Render) and resource (the wiki link graph) plus the output format (Mermaid diagram) and the node/edge semantics. An agent can distinguish it from wiki_ls, wiki_search, or code_map without opening a schema.

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?

The description implies two usage modes — full graph vs. a focused view around `center` within `depth` hops — which is useful implied guidance. But it names no alternatives and gives no explicit when-to-use/when-not criteria versus sibling tools like wiki_ls or code_map.

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