clariBI.com

verify_email

Complete clariBI signup by submitting the verification code plus a password. Returns an OAuth access_token for immediate use AND a long-lived MCP API key for persistent configuration. The new organization lands on the Trial tier (50 AI credits, 14 days).

Input Schema

TableJSON Schema

Name	Required	Description
`code`	Yes	6-digit verification code from the email.
`password`	Yes	A password for the new account. Must be at least 8 characters and pass Django's standard validators.
`pending_id`	Yes	The pending_id returned by register_account.

Output Schema

TableJSON Schema

Name	Required	Description
`tier`	Yes	New organization tier, always "trial".
`scope`	Yes	Space-separated granted scopes.
`user_id`	Yes
`expires_in`	Yes	Access-token lifetime in seconds.
`next_steps`	No
`token_type`	Yes	Always "Bearer".
`mcp_api_key`	Yes	Long-lived API key (claribi_mcp_...) for persistent client config.
`access_token`	Yes	OAuth bearer token for this conversation.
`mcp_api_key_id`	Yes
`organization_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "access_token": {
+      "description": "OAuth bearer token for this conversation.",
+      "type": "string"
+    },
+    "expires_in": {
+      "description": "Access-token lifetime in seconds.",
+      "type": "integer"
+    },
+    "mcp_api_key": {
+      "description": "Long-lived API key (claribi_mcp_...) for persistent client config.",
+      "type": "string"
+    },
+    "mcp_api_key_id": {
+      "format": "uuid",
+      "type": "string"
+    },
+    "next_steps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "organization_id": {
+      "type": "string"
+    },
+    "scope": {
+      "description": "Space-separated granted scopes.",
+      "type": "string"
+    },
+    "tier": {
+      "description": "New organization tier, always \"trial\".",
+      "type": "string"
+    },
+    "token_type": {
+      "description": "Always \"Bearer\".",
+      "type": "string"
+    },
+    "user_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "access_token",
+    "token_type",
+    "expires_in",
+    "scope",
+    "mcp_api_key",
+    "mcp_api_key_id",
+    "user_id",
+    "organization_id",
+    "tier"
+  ],
+  "type": "object"
+}

First observedJun 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations provide minimal signal (all false). The description adds valuable behavior: it returns an OAuth access_token and MCP API key, and places the org on Trial tier (50 credits, 14 days). It does not detail side effects like single-use codes, but the key behavioral outcomes are disclosed without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, efficiently front-loaded with the core action and followed by return value and account tier. Every sentence adds value with no redundancy or filler.

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?

The description covers the tool's purpose, return value, and post-condition (Trial tier), and an output schema exists to detail the return structure. It does not explicitly state the dependency on register_account, but the schema's pending_id reference and sibling context make it adequately complete for a signup completion tool.

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% for all parameters, so the baseline is 3. The description adds no extra parameter semantics beyond mentioning 'verification code plus a password' and does not reference pending_id, but the schema fully documents each field with constraints and origins.

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 description clearly states the specific action: 'Complete clariBI signup by submitting the verification code plus a password.' This uses a precise verb ('complete') and resource ('clariBI signup'), distinguishing it from siblings like register_account (which initiates signup) and other unrelated tools.

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?

The description implies usage context: it is the signup completion step, referencing the pending_id from register_account in the schema. It clearly indicates when to use, but does not explicitly state exclusions or alternatives. However, because it is uniquely paired with register_account, the guidance is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All clariBI.com tools Inspect

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

Need Help?