Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_public_proofs

Destructive

Update which verified proofs appear on a public profile, including each proof's visibility, masking level, and display order.

Instructions

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

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, or sign in with start_login — a session opens this tool — then call this tool again.

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. Changed5 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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"
+}
    • removedInput schema / properties / proofs / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / proofs / items / properties / display_order / maximum
      Added value: +9007199254740991
    • 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. First observedv1.1.0

TDQS

A3.5/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 operation. The description adds useful access requirements and lists the affected proof attributes, but it does not explain whether the supplied proofs array replaces all existing public proofs or what happens to omitted proofs.

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 followed by a compact access note. Both sentences earn their place and there is no unnecessary wording.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, annotations disclose destructiveness, and authentication is covered. Still, for a destructive public-profile mutation, the missing explanation of replacement behavior and the overlap with update_profile_proofs leaves a meaningful gap.

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 schema already documents every parameter and nested field. The description adds only high-level context about visibility, masking, and display order, without clarifying proof_order or replacement semantics beyond the schema.

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 specific verb and resource: updating which verified proofs are visible on the user's public profile, including visibility, masking, and display order. It is clear what the tool does, but it does not distinguish it from the very similarly named sibling update_profile_proofs.

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?

Usage is implied by the public-profile proof configuration context, and the access prerequisite is explained. However, there is no explicit guidance on when to use this instead of update_profile_proofs or other profile-related siblings.

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

Deploy Server

Other Tools