Skip to main content
Glama
Sign In

Proof Holdings

by holdings.proof
OverviewDiscussionsAdmin

list_verifications

Read-only

List verifications with optional filters. Returns paginated results.

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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_verifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
typeNoFilter by asset type
limitNoItems per page
statusNoFilter by status
channelNoFilter by channel

Output Schema

NameRequiredDescriptionDefault
dataYes
paginationYesPagination info in list responses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / channel / enum
      Previous value: -[
-  "sms",
-  "whatsapp",
-  "telegram",
-  "email"
-]New value: +[
+  "whatsapp",
+  "telegram",
+  "sms",
+  "email",
+  "dns",
+  "http",
+  "auto",
+  "github",
+  "google",
+  "facebook",
+  "x",
+  "linkedin",
+  "instagram",
+  "youtube",
+  "tiktok",
+  "ethereum",
+  "solana",
+  "bitcoin",
+  "coinbase",
+  "kraken",
+  "telegram_bot_token"
+]
    • removedInput schema / properties / external_user_id
      Removed value: -{
-  "description": "Filter by external user ID",
-  "type": "string"
-}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Filter by asset type",
+  "enum": [
+    "phone",
+    "email",
+    "domain",
+    "social",
+    "wallet",
+    "account",
+    "telegram_bot"
+  ],
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Paginated list of verifications",
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "channel": {
+            "type": "string"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "environment": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "identifier": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "verified_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "type",
+          "channel",
+          "status",
+          "environment",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": {},
+      "description": "Pagination info in list responses",
+      "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"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "pagination"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds value beyond that: it discloses that results are paginated and, importantly, that the tool requires Proof-account authentication and is not unlocked by start_login. That auth gotcha is exactly the kind of non-obvious behavior worth surfacing. It stops short of describing defaults for page/limit or total-count behavior, keeping it from 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?

Purpose and pagination are front-loaded in a single short sentence, and the ACCESS block is short and actionable. The access note is slightly disproportionate to the description body but every sentence (authenticate, then retry; start_login does not apply) carries operational value.

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

Completeness5/5

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

An output schema exists, so return shape need not be explained; annotations cover the safety profile; all five parameters are documented in schema. The remaining risk an agent faces — being unauthenticated and misrouting to start_login — is explicitly addressed, making the definition complete for correct invocation.

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 coverage is 100% with three enum-constrained filters fully documented, so the schema carries the semantics. The description only says 'optional filters' and adds no meaning about filter combination behavior, default page size, or whether filters are ANDed. Baseline 3 is appropriate here.

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 and resource ('List verifications') and states that filters are optional and results are paginated. It never distinguishes this from adjacent listing tools such as list_verification_requests, list_verified_users, or list_revoked_proofs, so the agent must infer the boundary from the name alone.

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

Usage Guidelines2/5

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

There is no guidance on when this listing is the right choice versus the many sibling listing tools (list_verification_requests, list_verified_users, list_revoked_proofs, get_verification). The only conditional instruction is about authentication ('start_login does NOT open this tool'), which is a setup prerequisite rather than use-vs-alternative guidance.

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