@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

create_circle

Create a named Circle of trusted contacts, optionally seeding initial members and their declared messenger channels so each contact can be invited to enroll.

Instructions

Create a Circle — a named group of trusted contacts (the people-primitive powering Proof-Me and Approvals-on-Circle). Optionally seed initial members; each member's declared channels are stored so they can be invited to enroll.

Agent usage: after creating a Circle, add members with add_circle_member (or seed them here), then invite_circle_member to mint the enrollment deep link each contact 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
`name`	Yes	Human-readable name for the Circle
`members`	No	Initial members (name + optional declared channels)
`owner_name`	No	How this Circle's members know its owner ("Dad", "Giorgi"). The bots name the owner by it; while it is empty they name nobody — the Circle's name labels the group, never the person. Trimmed by the API; null or an empty value clears it.
`profile_id`	No	Public profile (sub-account) to bind for branded messages — create-only
`proof_me_enabled`	No	Enable Proof-Me drills for this Circle

Output Schema

Name	Required	Description
`id`	No	MongoDB ObjectId
`name`	No
`status`	No	Lifecycle state of a Circle (archived = soft-retired)
`members`	No
`user_id`	No
`created_at`	No
`owner_name`	No	How this Circle's members know its owner; null when unset
`profile_id`	No
`updated_at`	No
`environment`	No
`member_count`	No
`proof_me_enabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.7.2Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / members / items / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "created_at": {},
+    "environment": {},
+    "id": {
+      "description": "MongoDB ObjectId"
+    },
+    "member_count": {},
+    "members": {},
+    "name": {},
+    "owner_name": {
+      "description": "How this Circle's members know its owner; null when unset"
+    },
+    "profile_id": {},
+    "proof_me_enabled": {},
+    "status": {
+      "description": "Lifecycle state of a Circle (archived = soft-retired)"
+    },
+    "updated_at": {},
+    "user_id": {}
+  },
+  "type": "object"
+}

Changed1 schema field changedv1.6.0Oct 16, 2026

addedInput schema / properties / owner_name

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 100,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How this Circle's members know its owner (\"Dad\", \"Giorgi\"). The bots name the owner by it; while it is empty they name nobody — the Circle's name labels the group, never the person. Trimmed by the API; null or an empty value clears it."
+}

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 goes further by disclosing the auth prerequisite, the fact that start_login will not satisfy it, and what happens to declared member channels (stored so members can be invited later). It does not cover duplicate-name behavior, idempotency, or what the create response contains, which the presence of an output schema partly excuses.

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?

Three short paragraphs, front-loaded with the definition, then the agent workflow, then access constraints — an agent reading only the first sentence already knows what the tool does. The access paragraph's restart instruction is slightly operationally verbose but earns its place by preventing a failed call.

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 create tool with five parameters, full schema descriptions, annotations, and an output schema, the description supplies exactly what structured fields cannot: the domain model, the follow-on workflow, and the auth gate. Nothing an agent needs before calling it 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 value by explaining that members may be seeded at creation as an alternative to add_circle_member and that their declared channels persist for later enrollment. It says nothing about profile_id or proof_me_enabled beyond what the schema already states.

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?

Names a specific verb and resource ("Create a Circle") and defines the resource in domain terms: a named group of trusted contacts powering Proof-Me and Approvals-on-Circle. That framing distinguishes it cleanly from list_circles, get_circle, update_circle and delete_circle without opening any schema.

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?

The "Agent usage" paragraph gives an explicit sequence: create, then add_circle_member or seed members here, then invite_circle_member to mint the enrollment link. It also states a hard exclusion — "start_login does NOT open this tool" — and the prerequisite (set PROOF_API_KEY and restart), which is more than most definitions offer.

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

Deploy Server