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

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_current_user

Read-only

Retrieves the signed-in user's account details, plan, and settings. Requires an active login session, which start_login and wait_for_login establish, to identify the current account.

Instructions

Get the signed-in user's account details, plan and settings. Needs a login session: call start_login, then wait_for_login until it reports success. An API key alone cannot read this — for the key's own account use get_self_api_key or get_settings.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
idNoMongoDB ObjectId
emailsNo
created_atNo
phone_numbersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "created_at": {},
+    "emails": {},
+    "id": {
+      "description": "MongoDB ObjectId"
+    },
+    "phone_numbers": {}
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds the crucial behavioral fact that authentication must come from a session rather than a key, plus two access paths (PROOF_API_KEY env var with restart, or sign-in). This is exactly the kind of constraint an agent cannot infer from the schema or annotations and would otherwise fail on repeatedly.

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 the sibling routing are front-loaded in the first sentence, which is ideal. The second paragraph restates the login requirement already given ('call start_login, then wait_for_login'), so the ACCESS block overlaps rather than strictly adding, costing a point.

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?

A zero-param read tool with an existing output schema needs only purpose and access conditions to be callable, and both are fully covered, including the environment-variable path. Nothing an agent needs at invocation time is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; nothing needs explaining and the description correctly does not invent parameter guidance. No additional value is possible on this dimension.

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?

States a specific verb and resource ('Get the signed-in user's account details, plan and settings') and explicitly distinguishes itself from the two nearest siblings, get_self_api_key and get_settings, which cover the API key's own account. An agent can pick the right tool without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite chain (start_login, then wait_for_login until it reports success), states a negative condition (an API key alone cannot read this), and names the alternatives to use in that case. When-to-use, when-not, and fallbacks are all present.

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