Skip to main content
Glama
Sign In
llm-wiki-mcp

llm-wiki-mcp

by kleinmatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_index

Retrieve a curated catalog of every wiki page with one-line summaries for quick navigation.

Instructions

Return the wiki index — a curated catalog of every page with one-line summaries. Read this first to navigate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It accurately states that the tool returns a catalog of all pages with summaries, implying a read-only action. However, it omits details like data freshness or performance characteristics, which are minor for this simple operation.

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?

The description is extremely concise at two sentences, with the main purpose front-loaded. Every phrase adds value, and there is no redundancy.

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?

Given the tool's simplicity (no parameters, has output schema), the description adequately explains what it returns and when to use it. The existence of an output schema likely details the return structure, so further elaboration is unnecessary.

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?

The input schema has zero parameters and schema description coverage is 100%, so the description does not need to add parameter info. Baseline score of 3 is appropriate as no additional meaning is required or provided.

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?

The description clearly states the tool returns the wiki index, a curated catalog of every page with one-line summaries, using specific verb 'Return' and resource 'wiki index'. It distinguishes from siblings like search_wiki and read_page by emphasizing it as a starting point for navigation.

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?

The description explicitly recommends 'Read this first to navigate', giving a clear use case for initial orientation. It does not mention when not to use it, but the sibling tools imply alternatives for specific search or page retrieval tasks.

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