@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

create_approval_channel

Creates a human-in-the-loop approval configuration that routes approval requests to Telegram, WhatsApp, or circle members and sets a default timeout.

Instructions

Create a HITL (Human-in-the-Loop) config. Defines which messaging channels receive approval requests and the default timeout.

Agent usage: After creating an approval channel, you must call request_approval_channel_authorization before it can be used with create_confirmation. For Telegram channels, use create_chat_id_discovery first to discover the user's chat ID, then include it in the channel config.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

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

Input Schema

Name	Required	Description
`name`	Yes	Human-readable name for this approval channel
`channels`	No	Messaging channels for approval requests (telegram or whatsapp). Either channels or circle_id is required.
`circle_id`	No	Route approvals through this circle's members instead of listed channels (24 hex characters)
`profile_id`	No	The sub-account (24 hex characters) whose branding the approval messages carry; omitted, the primary
`timeout_seconds`	No	Default timeout in seconds (60–86400, default: 3600)

Output Schema

Name	Required	Description
`id`	Yes	MongoDB ObjectId
`name`	No
`status`	Yes	Status of a HITL configuration
`keypair`	Yes	Encryption keypair metadata (null if not configured)
`user_id`	Yes	Owner user ID (useful for SDK encryption AAD)
`channels`	Yes
`circle_id`	No	Backing Circle for a circle-backed Approvals config (null for channel-list configs)
`created_at`	Yes
`profile_id`	No
`updated_at`	Yes
`environment`	Yes
`timeout_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.10.0Nov 13, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds real behavioral context beyond that — the two-step authorization model, the platform-specific prerequisite for Telegram, and an authentication/setup requirement that will otherwise make the call fail. This is precisely the kind of pre-call information an agent cannot infer from structured 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?

Two short paragraphs, purpose front-loaded and prerequisites grouped under an explicit 'Agent usage:' label. Every sentence carries operational weight — even the 'start_login does NOT open this tool' warning prevents a plausible false path.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with an output schema, five well-documented parameters, and no nested ambiguity, the description covers the prerequisites, the follow-up call, and the access blocker. Nothing an agent needs before invoking it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema baseline is 3, but the description adds meaning beyond it by explaining that a Telegram channel's chat_id must come from create_chat_id_discovery. It does not explain how channels and circle_id interact when both are supplied, leaving a small gap.

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

Purpose5/5

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

States a specific verb and resource ('Create a HITL (Human-in-the-Loop) config') and immediately narrows scope to what the config controls: which messaging channels receive approval requests and the default timeout. It also names the downstream consumer (create_confirmation) and the sibling authorizer (request_approval_channel_authorization), so the agent can place it in the workflow.

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

Usage Guidelines5/5

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

Explicit ordering guidance: request_approval_channel_authorization must be called before the channel works with create_confirmation, and for Telegram the agent must run create_chat_id_discovery first to obtain the chat_id. The access precondition (Proof account, PROOF_API_KEY, restart, and the explicit note that start_login does NOT unlock this tool) is a clear when-to-use gate.

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

Deploy Server