Skip to main content
Glama
Sign In

Proof Holdings

by holdings.proof
OverviewDiscussionsAdmin

get_profile

Read-only

Get a specific profile by ID. Returns full profile details including theme, custom links, and verification display settings.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYesProfile ID

Output Schema

NameRequiredDescriptionDefault
idYesMongoDB ObjectId
bioNo
themeYesProfile theme customization
usernameNoAbsent until a username is claimed
is_publicYes
avatar_urlNoA URL or a data URI; null once cleared
created_atYes
is_primaryYes
profile_idYesThe public id used in profile URLs
updated_atYes
view_countYes
email_themeYesTheme of this sub-account's emails; null when unset (read as `dark`).
is_businessYes
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.
custom_linksYes
display_nameNo
business_nameNo
public_proofsYesThe shown proofs, in the order the public profile shows them
support_emailYesSupport address shown in this sub-account's messages; null when unset.
show_delegationsYes
verification_levelYesAlways 'basic'; no levels are computed; removed in the next major.
show_proof_channelsYes
show_verification_datesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "A sub-account as its owner sees it",
+  "properties": {
+    "avatar_url": {
+      "description": "A URL or a data URI; null once cleared",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "bio": {
+      "type": "string"
+    },
+    "business_name": {
+      "type": "string"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "custom_links": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "_id": {
+            "type": "string"
+          },
+          "display_order": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "icon": {
+            "type": "string"
+          },
+          "is_visible": {
+            "type": "boolean"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "_id",
+          "title",
+          "url",
+          "is_visible",
+          "display_order"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "display_name": {
+      "type": "string"
+    },
+    "email_theme": {
+      "description": "Theme of this sub-account's emails; null when unset (read as `dark`).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "MongoDB ObjectId",
+      "type": "string"
+    },
+    "is_business": {
+      "type": "boolean"
+    },
+    "is_primary": {
+      "type": "boolean"
+    },
+    "is_public": {
+      "type": "boolean"
+    },
+    "profile_id": {
+      "description": "The public id used in profile URLs",
+      "type": "string"
+    },
+    "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"
+    },
+    "show_delegations": {
+      "type": "boolean"
+    },
+    "show_proof_channels": {
+      "type": "boolean"
+    },
+    "show_verification_dates": {
+      "type": "boolean"
+    },
+    "support_email": {
+      "description": "Support address shown in this sub-account's messages; null when unset.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "theme": {
+      "additionalProperties": {},
+      "description": "Profile theme customization",
+      "properties": {
+        "background_color": {
+          "type": "string"
+        },
+        "background_type": {
+          "type": "string"
+        },
+        "font_style": {
+          "type": "string"
+        },
+        "gradient_end": {
+          "type": "string"
+        },
+        "gradient_start": {
+          "type": "string"
+        },
+        "primary_color": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "username": {
+      "description": "Absent until a username is claimed",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verification_level": {
+      "description": "Always 'basic'; no levels are computed; removed in the next major.",
+      "type": "string"
+    },
+    "view_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "profile_id",
+    "is_primary",
+    "verification_level",
+    "is_business",
+    "public_proofs",
+    "proof_order",
+    "custom_links",
+    "theme",
+    "is_public",
+    "show_verification_dates",
+    "show_proof_channels",
+    "show_delegations",
+    "support_email",
+    "email_theme",
+    "view_count",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds value beyond that by disclosing the authentication prerequisite and the failure mode of the sibling start_login tool. It stops short of describing error behavior when the ID is invalid or whether the caller must own the profile.

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?

Two tight blocks: purpose first, then a clearly separated ACCESS note. Every sentence is load-bearing, including the parenthetical about the /mcp authentication path, and nothing is buried behind filler.

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?

For a one-parameter read tool with an output schema that already documents the return shape and annotations that declare read-only behavior, this covers the essentials including auth. The only missing piece is disambiguation from get_my_profile.

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?

There is a single parameter at 100% schema description coverage ("Profile ID"), so the schema already carries the semantics. The description adds no format, prefix, or scoping detail for profile_id, which is acceptable but not additive.

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 uses a specific verb+resource ("Get a specific profile by ID") and enumerates what comes back (theme, custom links, verification display settings). It does not, however, distinguish itself from the close sibling get_my_profile or from list_profiles, so an agent must infer which profile-lookup tool applies.

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 operational precondition (a Proof account is required, authenticate the client, start_login does not unlock this tool), which is genuinely useful. But there is no guidance on when to pick this over get_my_profile or list_profiles, which is the main selection ambiguity an agent faces here.

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