Tools

MCP tools, resources, and prompts -- how The Pantion Dialog connects to your coding agent.

On this page

The Pantion Dialog exposes its capabilities as MCP tools, resources, and prompts.

Tools

Dialog
pantion_startOpen the router -- guides you to the right action.
pantion_dialogStart a convergence dialog. Normal or automatic mode.
pantion_check-convergenceValidate structural convergence -- stamp, required fields, open questions.
pantion_save-canonWrite dialog + summary to disk.
pantion_resumeContinue a draft dialog across sessions.
Approve
pantion_approveApprove a converged canon with a human stamp. Required before build.
pantion_rejectReject a converged canon. Needs changes before it can proceed.
Build
pantion_translateGenerate spec files from a converged canon.
System
pantion_list-canonsList all canons in the project.
pantion_versionShow the installed Pantion version.

Modes

Every dialog runs in one of two convergence modes:

Mode What happens Best for
Normal You answer each question yourself, step by step Complex systems, precise control
Automatic Pantion generates the full dialog from your description Quick exploration, simple projects

Automatic mode in action

In automatic mode, Pantion generates a complete convergence dialog from a single description. You review and adjust.

I want to start an automatic Pantion dialog for a web alarm clock with multiple timers

Pantion generates:

ASSISTANT: What is the core intent?
PANTION: A browser-based alarm clock with multiple independent timers ⚡

A: What happens when a timer finishes?
PANTION: Audio alert + visual flash. Audio stops on click/tap. ⚡

A: How many timers can run simultaneously?
PANTION: No hard limit. UI scrolls. ⚡

A: What does this NOT do?
PANTION: No accounts, no server, no persistence across sessions ⚡

The ⚡ marks are conservative assumptions – decisions Pantion made for you. Review, adjust what you disagree with, and the canon is ready.

Souls

The Pantion Dialog supports souls – configurable interaction styles that change how the dialog is conducted without changing what is discussed.

Soul Style
default Clear, professional, systematic
beginner Extra explanation, less jargon
young Simple language for young builders

Souls are passed as a parameter when starting a dialog: soul: "beginner".

Typical workflow

graph LR A["start"] --> B["approve"] B --> C["translate"] C --> D["build"]
  1. Start – Describe what you want. The Pantion Dialog asks clarifying questions until convergence.
  2. Approve – Officially approve the converged canon to lock intent.
  3. Translate – Generate spec files from the converged canon.
  4. Build – Your coding agent builds from the canon and spec files. Point your agent at canon/<project>/spec/.