@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

get_circle

Read-only

Retrieves a Circle by ID, returning its members and per-member channel presence flags without exposing member identifiers.

Instructions

Get a Circle by ID. Returns the Circle including its members and per-member channel presence booleans (an identifier is NEVER returned — SEC-PM-006).

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	Default
`id`	Yes	Circle ID

Output Schema

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

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": {},
+  "description": "A Circle — a named group of trusted contacts",
+  "properties": {
+    "created_at": {
+      "type": "string"
+    },
+    "environment": {
+      "type": "string"
+    },
+    "id": {
+      "description": "MongoDB ObjectId",
+      "type": "string"
+    },
+    "member_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "members": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "enrolled_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "enrolled_phone_hint": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "has_telegram": {
+            "type": "boolean"
+          },
+          "has_whatsapp": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "last_verified_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "mesh_opt_out": {
+            "type": "boolean"
+          },
+          "mesh_opted_in": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "status",
+          "has_telegram",
+          "has_whatsapp",
+          "mesh_opted_in",
+          "mesh_opt_out",
+          "enrolled_phone_hint",
+          "enrolled_at",
+          "last_verified_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "owner_name": {
+      "description": "How this Circle's members know its owner; null when unset",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "profile_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "proof_me_enabled": {
+      "type": "boolean"
+    },
+    "status": {
+      "description": "Lifecycle state of a Circle (archived = soft-retired)",
+      "type": "string"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "user_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "user_id",
+    "name",
+    "owner_name",
+    "profile_id",
+    "environment",
+    "proof_me_enabled",
+    "status",
+    "member_count",
+    "members",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedv1.1.0Sep 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

readOnlyHint=true is already supplied, so the safety profile is free; the description goes further by disclosing the return shape (members and their per-channel presence booleans) and a privacy guarantee that no identifier is ever returned (SEC-PM-006). It also spells out the auth/troubleshooting behavior that annotations cannot express. Rate limits and failure modes remain undisclosed.

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?

Two tight paragraphs: the purpose and return contract come first, then the access constraint. The "SEC-PM-006" internal reference is mildly opaque jargon but costs little and signals a hard rule.

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

Completeness4/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 enumerated, yet the description still previews the important ones. Combined with the explicit auth prerequisite and the read-only annotation, an agent has what it needs to call this correctly; only cross-tool routing guidance is thin.

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

Parameters3/5

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

Schema coverage is 100% and the single id parameter is validated by a 24-hex-char pattern, so the schema does the heavy lifting. The description only says "by ID," adding no format or sourcing hints (e.g., where an ID comes from) beyond the schema. Baseline 3 is appropriate.

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?

"Get a Circle by ID" names a specific verb and resource, and the follow-up sentence describes what the payload contains (members plus per-member channel presence booleans). It is clearly distinct from list_circles/create_circle/update_circle, though it never names a 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 Guidelines4/5

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

The ACCESS block gives a concrete precondition (a Proof account, PROOF_API_KEY set, restart then retry) and explicitly rules out a tempting wrong path: start_login does NOT unlock this tool. What is missing is guidance on when to prefer this over list_circles or get_circle_member when the caller does not yet have an ID.

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

Deploy Server