Skip to main content
Glama
Sign In

Proof Holdings

by holdings.proof
OverviewDiscussionsAdmin

update_public_proofs

Destructive

Update which verified proofs are visible on the user's public profile, including visibility, masking, and display order.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), or sign in with start_login — a session opens this tool — then call this tool again.

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": {
      "proofs": "<proofs>"
    },
    "name": "update_public_proofs"
  }
}

Input Schema

NameRequiredDescriptionDefault
proofsYesArray of proof display configurations (max 50)
proof_orderNoWho orders the shown proofs: `default` (domain, social, Telegram bot, email, phone, wallet, then display_order) or `owner` (display_order alone). Omitted, the profile keeps its current setting.

Output Schema

NameRequiredDescriptionDefault
proof_orderYesWho decided the order of a profile's proofs. `default`: domain, social account, Telegram bot, email, phone, wallet, then each proof's `display_order`. `owner`: the owner's `display_order` alone — send it when the owner reorders. The first shown proof that is not hidden leads the profile's preview card, share tags and badge. Omitted on an update, the profile keeps its current setting.
public_proofsYesThe shown proofs, in the order the public profile shows them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / proof_order
      Added value: +{
+  "description": "Who orders the shown proofs: `default` (domain, social, Telegram bot, email, phone, wallet, then display_order) or `owner` (display_order alone). Omitted, the profile keeps its current setting.",
+  "enum": [
+    "default",
+    "owner"
+  ],
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "A sub-account's shown proofs after an update",
+  "properties": {
+    "proof_order": {
+      "description": "Who decided the order of a profile's proofs. `default`: domain, social account, Telegram bot, email, phone, wallet, then each proof's `display_order`. `owner`: the owner's `display_order` alone — send it when the owner reorders. The first shown proof that is not hidden leads the profile's preview card, share tags and badge. Omitted on an update, the profile keeps its current setting.",
+      "type": "string"
+    },
+    "public_proofs": {
+      "description": "The shown proofs, in the order the public profile shows them",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "asset_id": {
+            "type": "string"
+          },
+          "channel": {
+            "type": "string"
+          },
+          "delegate_type": {
+            "type": "string"
+          },
+          "delegation_id": {
+            "type": "string"
+          },
+          "display_order": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "display_value": {
+            "type": "string"
+          },
+          "is_revoked": {
+            "type": "boolean"
+          },
+          "is_visible": {
+            "type": "boolean"
+          },
+          "label": {
+            "type": "string"
+          },
+          "mask_level": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "verified_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "asset_id",
+          "type",
+          "display_value",
+          "verified_at",
+          "is_visible",
+          "display_order",
+          "mask_level"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "public_proofs",
+    "proof_order"
+  ],
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / proofs / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / proofs / items / properties / display_order / maximum
      Added value: +9007199254740991
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already mark this as a non-read-only, destructive mutation, and the description adds valuable authentication context that annotations do not cover. It does not clarify whether the proofs array replaces the existing public-proof configuration, which is important destructive behavior for an agent to understand.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose and then gives a compact access note. Both sentences earn their place: the first defines the operation, and the second prevents a common authentication failure.

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 a fully documented schema, an output schema, and annotations declaring the mutation profile, the description covers the essential purpose and authentication requirement. Its main remaining gap is not positioning the tool relative to the closely named update_profile_proofs sibling.

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 the detailed nested fields and proof_order enum are already documented in the schema. The description reinforces the main concepts but adds no syntax or behavioral detail beyond what the schema provides, making the baseline 3 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?

The description states a clear verb and resource: update verified proofs visible on the user's public profile, with visibility, masking, and display order. It is specific enough to understand the operation, but it does not distinguish itself from the sibling update_profile_proofs tool.

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 paragraph gives a useful precondition: a Proof account is required, and the client must authenticate or use start_login before calling. However, it does not explain when to use this tool instead of similar siblings such as update_profile_proofs, nor does it provide exclusions.

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

All Proof Holdings toolsInspect
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.

Resources