Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sapper Recall

sapper_recall

Find prior facts or intents similar to a free-text gist, then read the top match with sapper_doc to reuse learned knowledge.

Instructions

Find prior facts/intents similar to a free-text gist; read the top hit's doc with sapper_doc to reuse what was learned.

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": {
      "query": "<query>"
    },
    "name": "sapper_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoany
limitNo
queryYes
storeNo.sapper

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does convey that this is a similarity lookup returning ranked hits ('top hit') that are then read elsewhere. It does not state read-only safety, ranking/scoring semantics, cross-store behavior, or what an empty result looks like — notable gaps for an unannotated tool, though an output schema exists to cover result fields.

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 sentence that front-loads the core operation and ends with the actionable follow-up step. No filler, no repetition of the tool name, nothing that could be cut without losing meaning.

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?

The output schema covers return values, but for a 4-parameter search tool with zero schema descriptions, the description should explain the kind filter, limit, and store scope. It explains none of these, so an agent cannot confidently choose parameter values beyond the required query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters. The description hints at 'query' ('free-text gist') and at 'kind' via 'facts/intents', but never explains `kind`, `limit` (default 5), or `store` (default '.sapper'), leaving most parameter meaning to be inferred from bare names and defaults.

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 gives a specific verb and resource: 'Find prior facts/intents similar to a free-text gist.' It also names the natural follow-up (sapper_doc) so an agent can distinguish retrieval from document reading, though it doesn't distinguish itself from other sapper_* lookup siblings such as sapper_fact or sapper_intent.

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?

'Reuse what was learned' implies a when-to-use context (before re-deriving prior work), and the pointer to sapper_doc states the follow-up step. However, there is no explicit when-not guidance, no statement of what to do when no similar prior work exists, and no comparison to any alternative retrieval 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