Skip to main content
Glama
Sign In

Agent Wikis

by io.github.tonbistudio
OverviewDiscussionsAdmin

List wikis

list_wikis
Read-onlyIdempotent

List all available wikis with metadata: slug, title, description, tags, status, last updated, document count, and scope (what each wiki covers, what it does NOT cover, and how current it is — use this to pick a wiki and to decide when to fall back to web search). Includes "coming soon" placeholders, marked by status.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious behavior: the list includes 'coming soon' placeholders flagged by status, and the `scope` field includes negative coverage ('what it does NOT cover') and freshness, which prevents an agent from assuming every listed wiki is usable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and the returned metadata, then the one piece of decision guidance. The long parenthetical explaining `scope` is dense but each clause carries information an agent needs, so nothing is clearly wasteful.

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?

With no output schema, the description must carry the return-value burden and it largely does by naming the fields available. The main residual gap is whether document bodies are included or whether a follow-up read call is required — likely a different tool, but not stated.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description instead spends its words on return-field meaning, which is the relevant substitute for a no-arg tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('List all available wikis') and enumerates exactly what comes back (slug, title, description, tags, status, last updated, document count, scope). It stops short of naming the natural follow-up sibling (open_wiki) for reading a wiki's contents, so differentiation from siblings is implied rather than stated.

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?

It gives concrete decision guidance — use the `scope` field to pick a wiki and to decide when to fall back to web search — which is exactly the routing choice an agent faces here. It does not say what to call after choosing a wiki, so the guidance covers selection but not the rest of the workflow.

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

All Agent Wikis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources