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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_verified_users

Read-only

Lists verified users grouped by external_user_id and shows all verifications per user for account review.

Instructions

List verified users grouped by external_user_id. Shows all verifications per user.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
limitNoItems per page

Output Schema

NameRequiredDescriptionDefault
dataNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {},
+    "pagination": {}
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the bar is lower, and the description still adds non-obvious context: results are grouped rather than flat, and the tool is gated behind an API key that requires a server restart. The restart requirement in particular is behavior an agent cannot learn from annotations or schema.

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?

Two short blocks, front-loaded with what the tool returns before the access caveat. Wording is tight, though the instruction to "restart this server" is slightly awkward as a tool description rather than a doc note.

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?

Output schema exists, so return shape needn't be described, and the grouping semantics plus auth prerequisite fill the main gaps. The only missing piece for a list tool in a dense sibling set is explicit routing guidance versus the other verification-listing tools.

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% and both parameters (page, limit) carry their own descriptions and bounds, so the schema does the heavy lifting. The description adds nothing about pagination behavior or default page size, so baseline 3 applies.

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?

States a specific verb and resource ("List verified users") plus a distinctive shaping detail: results are grouped by external_user_id with all verifications per user. That distinguishes it from get_verified_user (singular) and list_verifications, though it never names those siblings explicitly.

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 real prerequisite (a Proof account, PROOF_API_KEY set, server restart) and preempts a likely wrong turn by saying start_login does NOT open this tool. However, there is no guidance on when to choose this over list_verifications, get_verified_user, or list_verification_requests, so the selection logic among siblings is left to inference.

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