SapperMCP

Overview Schema Source Related Servers Discussions Admin

Sapper Auto

sapper_auto

Automate graph goal pursuit by reasoning, exploring, optionally verifying, and looping until the goal, step limit, or deadline is reached.

Instructions

Drive a graph toward its goal autonomously: reason -> explore -> optional verify, looping until max-steps, the goal, or the deadline (like sapper auto).

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": "sapper_auto"
  }
}

Input Schema

Name	Required	Description	Default
`cwd`	No
`model`	No
`store`	No		.sapper
`verify`	No	verify each explore result
`dry_run`	No	reason only, no explore
`minutes`	No
`timeout`	No
`deadline`	No
`max_steps`	No
`templates`	No
`background`	No	run in a PTY session (recommended for real runs); poll with read_session_output
`max_explore`	No
`exec_timeout`	No	sync-mode cap (default 30 min)
`skip_permissions`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.9/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 does disclose the loop's termination conditions (max-steps, goal, deadline) and that verification is optional. It stays silent on the important behavioral facts surfaced only in the schema — PTY/background execution, permission skipping, and that this is a long-running, likely costly autonomous agent.

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?

A single tight sentence, front-loaded with the core action and followed by the loop mechanics. Nothing is wasted, though it is arguably too terse for a 14-parameter autonomous runner.

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 described. But for a complex, long-running autonomous tool with 14 loosely documented parameters and no annotations, the description omits execution mode, permission implications, and parameter guidance that an agent needs before calling it.

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 coverage is only 29% across 14 parameters, so the description must compensate and largely does not. It touches on max-steps, goal, deadline, and verify, but leaves cwd, model, store, templates, skip_permissions, exec_timeout, and the dry_run/background distinction unexplained.

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 verb and resource ('Drive a graph toward its goal autonomously') and outlines the internal loop (reason -> explore -> optional verify). This is clearly distinct from the sapper_* utility siblings, though it never names an alternative explicitly.

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 or when-not-to-use guidance. The parenthetical 'like `sapper auto`' anchors it to a known CLI behavior but does not tell an agent when to prefer this over sapper_dispatch, sapper_sweep, or a manual explore loop.

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

Deploy Server