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

mcp-llm-wiki

by RickyKleinhempel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read recent log entries

wiki_read_log
Read-only

Retrieve recent wiki log entries, newest first, to review changes and restore context at the start of a session.

Instructions

Return the latest log.md entries, newest first - useful at the start of a session.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of entries (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover the read-only safety profile (readOnlyHint=true). The description adds value by disclosing the 'newest first' ordering and the specific log.md resource, but it does not mention return format, pagination behavior, or error conditions. This is adequate but not rich.

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 with zero filler. The core function ('Return the latest log.md entries, newest first') comes first, followed by the usage hint. Every word earns its place.

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?

This is a simple tool with one optional parameter, read-only annotations, and no output schema. The description covers purpose, ordering, and typical usage. A minor gap is the lack of detail on what an 'entry' contains, but the low complexity makes this acceptable.

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 100% coverage: the only parameter 'limit' is fully described with type, min/max, and default. The description does not add any parameter-specific meaning, so the baseline score of 3 applies.

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 states a specific verb ('Return'), a concrete resource ('log.md entries'), and an ordering guarantee ('newest first'). This clearly distinguishes it from siblings like wiki_read_page or wiki_search, which operate on different resources.

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 provides a clear usage context: 'useful at the start of a session.' However, it does not explicitly name alternatives or state when not to use this tool, stopping short of a perfect score.

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