@proof-holdings/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

list_circles

Read-only

Retrieve Circles with optional status, environment, or profile filters, returning paginated results and excluding archived Circles unless explicitly requested.

Instructions

List Circles with optional filters. Archived Circles are excluded by default; pass status="archived" to surface them. Returns paginated results.

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
`page`	No	Page number (default 1)
`limit`	No	Items per page (default 20, max 100)
`status`	No	Filter by status (archived excluded unless requested)
`profile_id`	No	Filter by bound public profile (sub-account)
`environment`	No	Filter by environment (production or test)

Output Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	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": "Paginated list of Circles",
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "created_at": {
+            "type": "string"
+          },
+          "environment": {
+            "type": "string"
+          },
+          "id": {
+            "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": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "profile_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "proof_me_enabled": {
+            "type": "boolean"
+          },
+          "status": {
+            "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"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "properties": {
+        "limit": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "page": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "total": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "total_pages": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "page",
+        "limit",
+        "total",
+        "total_pages"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "pagination"
+  ],
+  "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?

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the non-obvious default-filtering behavior (archived excluded) and notes results are paginated. It also discloses the auth prerequisite that a caller must satisfy before the call will succeed, which is exactly the kind of context annotations cannot convey.

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 front-loaded sentences cover behavior and one short access block covers prerequisites; nothing is padded. The access sentence is slightly verbose in its step-by-step instructions, but it earns its place because it prevents a futile call.

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?

With an output schema present and 100% parameter documentation, the description only needs to add filtering defaults and access requirements, and it does both. A brief note on result ordering or total-count fields would make it fully complete, but nothing needed to call it correctly is missing.

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 description coverage is 100%, so page, limit, status, profile_id, and environment are already documented in the input schema, establishing a baseline of 3. The description restates the status filter's archived behavior but adds no new detail on page/limit bounds, profile_id format, or environment semantics beyond what the schema provides.

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?

The description opens with a specific verb+resource: "List Circles with optional filters," which cleanly separates it from get_circle, create_circle, and update_circle among the siblings. It does not explicitly name those siblings, so it stops short of a 5.

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?

It gives a concrete usage rule — archived Circles are hidden unless status="archived" is passed — plus an explicit exclusion telling the agent that start_login does NOT unlock this tool and that PROOF_API_KEY must be configured instead. This is strong routing guidance, though it does not enumerate alternate listing/pagination strategies.

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

Deploy Server