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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search

Read-only

Find account-scoped records across verification requests, verifications, HITL, confirmations, authorizations, and API keys via case-sensitive prefix matching; recipient IDs stay masked.

Instructions

Prefix-anchored global account search across six resource buckets (verification_requests, verifications, hitl, confirmations, authorizations, api_keys). Case-sensitive prefix match over indexed plaintext fields only; recipient identifiers are masked. Results are scoped to the authenticated account.

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
qYesPrefix-anchored search query (minimum 3 characters)
typeNoNarrow the search to a single result bucket
limitNoMax results per bucket (default 10, max 25)
environmentNoScope results to test or production data (default: production)

Output Schema

NameRequiredDescriptionDefault
dataNo
totalNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.2/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses real behavioral traits: matching is case-sensitive and prefix-anchored (not substring), only indexed plaintext fields are searchable, recipient identifiers come back masked, and corrects an easy assumption by stating start_login does not unlock this tool. It does not describe result ordering or the empty-result case, which keeps it off 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?

Two short paragraphs with the capability statement front-loaded and the access prerequisite separated out, so an agent can read the first line and act. The uppercase ACCESS header is functional rather than filler, though the setup instructions are somewhat verbose relative to the search semantics.

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?

For a four-parameter read tool with an output schema, full annotation of read-only behavior, and complete schema coverage, the description covers everything an agent needs: what is searched, matching rules, masking of sensitive fields, account scoping, and the authentication prerequisite that otherwise would cause repeated failed calls.

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 q, type, limit, and environment, and the description repeats the six enum values already present in the schema. It does add meaning for `q` by clarifying the matching is case-sensitive prefix rather than free-text, but adds nothing on limit or environment defaults. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource ("Prefix-anchored global account search") and enumerates the six buckets it covers, which lets an agent distinguish it from the many per-resource list_* siblings (list_verifications, list_confirmations, list_api_keys). The scope (account-wide, authenticated account only) is stated up front.

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

Usage Guidelines4/5

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

It gives clear operating context: use it for prefix matching across all six buckets, and the `type` field narrows to one bucket. The ACCESS note explicitly rules out start_login as a path to enabling this tool, which prevents a plausible wrong turn. It stops short of explicitly stating when to prefer this over a specific list_* sibling when the bucket is already known.

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