mindyard

List wikis

list_wikis

Read-only

Lists the caller's wikis as id, label, and description so you can pick the wiki id every other tool requires. Call it first in a session; an empty list means no wiki is set up.

Instructions

List the caller's wikis as [{id, label, description}].

Call it first in a session: every other tool takes one of these ids as 'wiki'. An empty list means no wiki is set up for this account.

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": "list_wikis"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 11, 2026

TDQS

A4.7/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, so the safety profile is covered. The description adds genuine behavioral context beyond that: an empty list is a meaningful signal that no wiki exists for the account, and the returned ids are the join key for all later calls. It does not mention scoping or auth, but with annotations present that is a minor gap.

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 short sentences, front-loaded with purpose and return shape, then ordering guidance, then empty-state meaning. No filler and nothing redundant.

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 zero-param read tool with an output schema already documenting return values, the description covers everything an agent needs: what it returns, that it must be called first, and how to interpret an empty result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the schema baseline is 4. The description usefully explains how the output field 'id' becomes the 'wiki' parameter of other tools, which is semantic context an agent needs even though there are no inputs to document.

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 ('List the caller's wikis') and even gives the returned object shape {id, label, description}, which immediately distinguishes it from siblings like list_pages or search_wiki.

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?

Explicitly prescribes ordering: 'Call it first in a session: every other tool takes one of these ids as wiki.' This tells the agent both when to use it and why, removing any ambiguity about prerequisites for the other tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server