SapperMCP

Overview Schema Source Related Servers Discussions Admin

Sapper Kb

sapper_kb

Store, search, and organize reusable notes in a shared offline knowledge base so you can add entries, filter by tags, import Markdown files, and retrieve full details.

Instructions

Shared offline knowledge base (like sapper kb).

Actions: add target=title; description/detail/tags/commands/source opts search target=query (first tag filters; limit applies) show target=kb id (e.g. kb001) -> full entry list browse entries (tags filter) import target=.md file or dir -> one entry per file root print the kb root dir

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": {
      "action": "<action>"
    },
    "name": "sapper_kb"
  }
}

Input Schema

Name	Required	Description	Default
`root`	No
`tags`	No
`limit`	No
`action`	Yes
`detail`	No
`source`	No
`target`	No
`commands`	No
`description`	No
`detail_file`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It notes that the KB is shared and offline and that import creates one entry per file, but it does not disclose write side effects, overwrite behavior, permissions, or other mutation risks for add and import.

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?

The description is compact and front-loaded as an action map, with each action on its own line. Some telegraphic wording such as 'opts' and arrow notation reduces clarity slightly, but there is little wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex ten-parameter, multi-action tool with write operations and no annotations, and the schema descriptions are absent. The description covers core action semantics but is not complete enough about parameter behavior, action constraints, or mutation side effects, even though an output schema exists.

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?

Schema description coverage is 0%, so the description must compensate for ten undocumented parameters. It usefully maps target for each action and mentions tags, limit, description, detail, commands, and source, but leaves detail_file and the root parameter largely unexplained and gives only vague semantics for several options.

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 states a specific resource, a shared offline knowledge base, and enumerates its actions. It is clear what the tool does, though it does not distinguish it from similarly named siblings such as sapper_doc or sapper_recall.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The action list implies when each internal action should be used, including target semantics for add, search, show, list, import, and root. However, it gives no explicit guidance on when to choose this tool over sibling tools or when not to use it.

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

Deploy Server