Skip to main content
Glama
Sign In
aiwiki-mcp

aiwiki-mcp

by XuebinMa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Get AiWiki entry

aiwiki_get_entry

Fetch full markdown of an AiWiki entry by ID, including mechanism analysis, consequences, best practices, and verifiable sources.

Instructions

Fetch the full markdown of one AiWiki entry by id (as returned by aiwiki_search). Entries include mechanism analysis, consequences, best practices, and verifiable sources.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "aiwiki_get_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntry id, e.g. "context-rot"
langNoContent language (default zh; falls back to zh if en missing)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 the burden. It discloses the output format ('full markdown') and content structure ('mechanism analysis, consequences, best practices, verifiable sources'), but does not mention error handling or language fallback (although the fallback is in the schema). This adds some transparency but not exhaustive detail.

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 two sentences with no filler. The key action and resource are front-loaded, and the second sentence explains entry content, efficiently using the space.

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 (id + optional lang, no output schema), the description is complete enough. It specifies what the entry contains and that the output is markdown. It does not discuss edge cases, but for a basic retrieval tool this is acceptable.

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?

Schema coverage is 100% for both parameters, so the baseline is 3. The description adds semantic value by clarifying the id is 'as returned by aiwiki_search', linking it to the search tool's output. This enriches the parameter meaning beyond the schema description.

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 specifies the action ('Fetch the full markdown') and the resource ('one AiWiki entry by id'). It also differentiates from the sibling aiwiki_search by indicating the id comes from that search tool.

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 phrase 'as returned by aiwiki_search' provides clear context that this tool is used after searching. It does not explicitly state when not to use it, but the context is sufficient for a simple fetch tool.

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