Proof Holdings

invite_circle_member

Mint a single-use enrollment invite for a Circle member. Returns Telegram + WhatsApp deep links and a QR code; the member taps the channel-matched link to bind their messenger identity to the Circle.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), 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": {
      "id": "<id>",
      "member_id": "<member_id>"
    },
    "name": "invite_circle_member"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Circle ID
`member_id`	Yes	Member ID to invite

Output Schema

Name	Required	Description
`token`	No
`qr_code`	No	QR code data URL for the primary deep link
`qr_text`	No	UTF-8 text representation of the QR code
`member_id`	No	MongoDB ObjectId
`expires_in`	No
`telegram_deep_link`	No
`whatsapp_deep_link`	No
`suggested_share_text`	No	Suggested message to forward with the invite

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "expires_in": {},
+    "member_id": {
+      "description": "MongoDB ObjectId"
+    },
+    "qr_code": {
+      "description": "QR code data URL for the primary deep link"
+    },
+    "qr_text": {
+      "description": "UTF-8 text representation of the QR code"
+    },
+    "suggested_share_text": {
+      "description": "Suggested message to forward with the invite"
+    },
+    "telegram_deep_link": {},
+    "token": {},
+    "whatsapp_deep_link": {}
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare a non-destructive mutation, and the description goes well beyond them: it states the invite is single-use, names the return artifacts (Telegram + WhatsApp deep links and a QR code), and explains the binding flow. It also foregrounds the Proof-account auth requirement and the specific failure/retry path. It does not cover re-invocation or idempotency behavior, keeping it below a 5.

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?

The description is front-loaded with the core action and outcome in one sentence, then a separate ACCESS paragraph for the prerequisite. Every sentence earns its place, though the ACCESS paragraph is somewhat verbose relative to the core purpose.

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 both params fully described, the description need not explain return shapes yet still names the key artifacts. Auth and the binding flow are covered. The only material omission is sibling disambiguation against add_circle_member, which prevents a full 5.

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?

Both parameters are fully documented in the schema (Circle ID, Member ID to invite) with 24-hex patterns, so coverage is 100% and the schema carries the load. The description adds no format or constraint detail about id or member_id beyond what the schema already states. 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?

Opens with a specific verb and resource ('Mint a single-use enrollment invite for a Circle member') and describes the concrete outcome (channel-matched deep links binding a messenger identity to the Circle). This is far more informative than a bare name restatement. However, it does not explicitly differentiate from the sibling add_circle_member, leaving the agent to infer the boundary.

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

Usage Guidelines3/5

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

The ACCESS block gives a clear prerequisite and recovery path (authenticate, then call again, and start_login does NOT open this tool), which is useful operating guidance. But it never states when to use this versus add_circle_member or add_circle_member_channel — the alternatives that share the invite/member space — so selection guidance is only implied.

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

All Proof Holdings tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.