Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sapper Confirm

sapper_confirm

Confirms a pending intent by ID that was created with confirm=True, allowing the action to proceed; optionally reads from a specified store.

Instructions

Confirm an intent that was created with confirm=True.

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

Input Schema

NameRequiredDescriptionDefault
idYes
storeNo.sapper

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says nothing about what 'confirming' actually does — whether it executes/commits the pending intent, whether the action is irreversible, what happens on a wrong or expired id, or whether it requires approval state. For a state-changing confirmation step with zero annotation coverage, this is a significant gap.

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 short sentence with no filler, and the key precondition (confirm=True) is front-loaded. The brevity is partly under-specification rather than pure efficiency, but there is no wasted wording to trim.

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. However, for a confirmation/mutation action the description omits the side effects, the meaning of both parameters, and error conditions — the essentials an agent needs before invoking 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 description coverage is 0%, so the description must compensate for both parameters and does not. It never explains the format or source of the required 'id', and never mentions 'store' at all, even though that is a non-obvious filesystem path defaulting to '.sapper' that an agent could easily mis-set.

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 names a specific verb ('Confirm') and a specific resource ('an intent'), and adds the precondition that the intent must have been created with confirm=True. That condition meaningfully distinguishes it from a plain intent-creation tool, though it does not name any sibling explicitly.

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?

Usage is implied rather than stated: the agent can infer this is called after creating an intent with confirm=True. There is no explicit guidance on when to call it versus alternatives such as sapper_intent, sapper_done, or sapper_complete, and no statement of what to do if the intent was not created with confirm=True.

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