Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sapper Init

sapper_init

Creates a fact-intent graph from a one-line terminal goal, letting you set the graph directory, record the task origin, and optionally overwrite an existing graph.

Instructions

Create a fact-intent graph (like sapper init --goal).

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": {
      "goal": "<goal>"
    },
    "name": "sapper_init"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesthe terminal goal, one line
forceNooverwrite an existing graph (destructive)
storeNograph dir to create (default .sapper).sapper
originNowhere this task came from

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does very little with it. It implies a write/bootstrap operation but never states that it establishes state other tools depend on, what happens if a graph already exists, or that force overwrites destructively (that information exists only in the schema).

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?

One short sentence with the verb and resource front-loaded, no filler or redundancy. Its brevity is efficient, though it borders on under-specification for an initialization tool.

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?

An output schema exists so return values need not be explained, but this is a state-creating initialization tool in a large sibling family and the description says nothing about prerequisites, ordering, or what the graph enables. For a tool that likely gates all other sapper_* operations, that is a significant omission.

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 100%, so all four parameters including goal, force, store, and origin are already documented, which sets the baseline at 3. The description adds nothing beyond that—the `--goal` comparison restates rather than clarifies the goal parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Create a fact-intent graph"), so the basic action is identifiable. However, "fact-intent graph" is unexplained jargon, and the parenthetical CLI echo (`sapper init --goal`) adds no meaning an agent can act on. It also gives no hint of how this differs from siblings such as sapper_graph, sapper_intent, or sapper_setup.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says this should be run first, before which other operations, or as an alternative to sapper_setup or sapper_graph. The word "init" weakly implies bootstrapping, but no condition or exclusion is stated.

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