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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_add_email

Initiates adding a new email address by sending an OTP and returning a session ID for verification.

Instructions

Start adding a new email address. Sends an OTP code to the email. Returns a session ID to verify with.

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
emailYesEmail address to add

Output Schema

NameRequiredDescriptionDefault
emailYes
statusYes
channelYes
email_sentYesWhether the code went out; the session is started either way
expires_atYes
session_idYes
email_errorNoWhy the code did not go out; present only when `email_sent` is false
instructionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / email / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "An email-add session: a code was emailed to the address",
+  "properties": {
+    "channel": {
+      "type": "string"
+    },
+    "email": {
+      "type": "string"
+    },
+    "email_error": {
+      "description": "Why the code did not go out; present only when `email_sent` is false",
+      "type": "string"
+    },
+    "email_sent": {
+      "description": "Whether the code went out; the session is started either way",
+      "type": "boolean"
+    },
+    "expires_at": {
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    },
+    "session_id": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "session_id",
+    "email",
+    "channel",
+    "status",
+    "expires_at",
+    "instructions",
+    "email_sent"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, non-destructive mutation; the description adds the important behavioral facts beyond that — an actual OTP email is dispatched to the target address and a session ID is produced as the handle for the next step. It does not cover OTP expiry, retry/rate-limit behavior, or the existence of resend_email_otp, leaving some operational context unstated.

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?

The core behavior is front-loaded in the first two sentences and the access prerequisite is broken out as a separate labeled block, which is easy to scan. The ACCESS paragraph is slightly verbose for a precondition but each clause is actionable.

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?

An output schema exists, so return values need no explanation, and the description covers the two things an agent must know: authentication gating and the session-ID handoff to verification. Missing only edge-case behavior such as duplicate emails or OTP lifetime, which keeps it from a 5 for a flow-starting mutation.

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 required parameter with 100% schema coverage including a format and regex pattern, so the schema already carries the semantics. The description adds nothing about the email argument itself (e.g., deliverability or normalization rules), so the 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 ('Start adding a new email address') and adds two concrete behaviors: an OTP is sent and a session ID is returned for verification. This clearly separates it from sibling flows such as setup_domain_email, add_domain, or start_add_phone, 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 Guidelines4/5

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

Provides a clear precondition chain: you need a Proof account, either via PROOF_API_KEY or by signing in with start_login, and it notes that a session opens this tool, so the agent knows to retry after login. It stops short of explicit exclusions (e.g., what to do if the email already exists) or naming the follow-up verification tool.

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