@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

add_circle_member

Add a pending Circle member by name with an optional WhatsApp phone; capture their messenger identity later via a single-use enrollment link.

Instructions

Add a pending member to a Circle by name, with an optional pre-declared WhatsApp phone. The Telegram chat id is captured later when the member taps the enrollment deep link.

Agent usage: after adding a member, call invite_circle_member to mint the single-use enrollment link the member taps to bind their messenger identity.

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.

Input Schema

Name	Required	Description
`id`	Yes	Circle ID to add the member to
`name`	Yes	Display name of the member
`whatsapp_phone`	No	E.164 WhatsApp phone with a leading + (optional, declared)

Output Schema

Name	Required	Description
`id`	No	MongoDB ObjectId
`name`	No
`status`	No
`enrolled_at`	No
`has_telegram`	No	Whether the member has a Telegram channel (declared or verified)
`has_whatsapp`	No	Whether the member has a WhatsApp channel (declared or verified)
`mesh_opt_out`	No	The member sent /opt_out: they receive no drills, reminders or checks they did not start themselves
`mesh_opted_in`	No
`last_verified_at`	No	When this member last CONFIRMED an identity check asked of them — i.e. last proved it was them. Null until they have.
`enrolled_phone_hint`	No	Masked form of the phone the contact proved when they enrolled (the Telegram shared contact or the WhatsApp sender) — country prefix and last four digits only, never the full number. Lets the owner see who actually joined. Null until the member enrolls, and for members enrolled before it was recorded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.7.2Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "enrolled_at": {},
+    "enrolled_phone_hint": {
+      "description": "Masked form of the phone the contact proved when they enrolled (the Telegram shared contact or the WhatsApp sender) — country prefix and last four digits only, never the full number. Lets the owner see who actually joined. Null until the member enrolls, and for members enrolled before it was recorded."
+    },
+    "has_telegram": {
+      "description": "Whether the member has a Telegram channel (declared or verified)"
+    },
+    "has_whatsapp": {
+      "description": "Whether the member has a WhatsApp channel (declared or verified)"
+    },
+    "id": {
+      "description": "MongoDB ObjectId"
+    },
+    "last_verified_at": {
+      "description": "When this member last CONFIRMED an identity check asked of them — i.e. last proved it was them. Null until they have."
+    },
+    "mesh_opt_out": {
+      "description": "The member sent /opt_out: they receive no drills, reminders or checks they did not start themselves"
+    },
+    "mesh_opted_in": {},
+    "name": {},
+    "status": {}
+  },
+  "type": "object"
+}

First observedv1.1.0Sep 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the meaningful state model (member starts pending, Telegram chat id is bound later via the enrollment deep link) and the auth gate. It does not mention rate limits, duplicate-name behavior, or whether the WhatsApp phone must match at enrollment time, leaving a few behavioral questions open.

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?

Front-loaded with the action, then workflow, then access, which is the right order for an agent. There is mild redundancy between 'the Telegram chat id is captured later when the member taps the enrollment deep link' and the 'mint the single-use enrollment link the member taps to bind their messenger identity' sentence in the usage note.

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 three-parameter mutation with an output schema already present, the description covers the full lifecycle: prerequisite auth, what state the member lands in, and the required follow-up call. Nothing an agent needs to invoke 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 coverage is 100%, so the baseline is 3; the description still adds meaning by framing name as the sole identity signal and the phone as 'pre-declared' rather than verified, and by situating the chat id as a later-bound value not passed here. It stops short of explaining format edge cases (e.g., name collisions), which the schema handles only via min/max length.

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 ('Add a pending member to a Circle') plus the key scoping detail that the member is pending and identified by name, with an optional pre-declared WhatsApp phone. This clearly separates it from sibling tools like invite_circle_member (mints the link), add_circle_member_channel (binds a channel), and create_circle_member_drill (test flow).

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?

Gives an explicit sequencing rule ('after adding a member, call invite_circle_member to mint the single-use enrollment link') and a negative case ('start_login does NOT open this tool'), which prevents a plausible wrong path. Prerequisites (Proof account + PROOF_API_KEY) are spelled out with the remedy.

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

Deploy Server