Widely

Open a white-label app account

open_platform_account

Idempotent

Opens a swift_platform account: the company that will own a white-label app. No sign-in. Omitted confirm returns a preview and does not create the account. True creates the company and emails a code. The account cannot be used until confirm_platform_email. An email that already belongs to a user opens another company on that same user. It does not create a second user, and it does not change that user's password. Password is optional. When it is omitted, sign-in is Google or the password reset flow. The password is not returned, logged, or emailed. Card numbers are not accepted. It does not create the people who will use the app. idempotency_key is required when confirm is true. The same idempotency_key repeats the same result instead of opening a second account. When the result says the account is on this connection, refresh tools, call get_account without an account to list them, then pass account by name. When it is not, add it from Connected apps, or reconnect and tick it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>",
      "email": "<email>",
      "first_name": "<first_name>",
      "last_name": "<last_name>"
    },
    "name": "open_platform_account"
  }
}

Input Schema

Name	Required	Description
`email`	Yes
`confirm`	No	Omitted returns a preview on every client. True opens the account.
`currency`	No	GBP, EUR, USD, or ILS. Omitted uses EUR.
`password`	No	Optional. At least 8 characters when set. Omitted uses the normal signup password. An existing user keeps their password. Never emailed or returned.
`last_name`	Yes
`first_name`	Yes
`company_name`	Yes
`phone_number`	No
`idempotency_key`	No	Repeats the same result instead of opening a second account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026

changedInput schema / properties / idempotency_key / description

Previous value: -"Repeats the same result instead of charging again."New value: +"Repeats the same result instead of opening a second account."

changedInput schema / properties / password / description

Previous value: -"At least 8 characters. Not stored in the result."New value: +"Optional. At least 8 characters when set. Omitted uses the normal signup password. An existing user keeps their password. Never emailed or returned."

changedInput schema / required

Previous value: -[
-  "company_name",
-  "email",
-  "password",
-  "first_name",
-  "last_name"
-]New value: +[
+  "company_name",
+  "email",
+  "first_name",
+  "last_name"
+]

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses that the account is inert until confirm_platform_email, that an email already owned by a user attaches a new company to that existing user without resetting the password, that the password is never returned/logged/emailed, and that card numbers are rejected. It also explains the idempotency requirement tied to confirm=true and what a repeated key does. These are real operational facts not derivable from the annotation set.

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

Conciseness3/5

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

The lead sentence front-loads the action and the preview/confirm distinction correctly, but several sentences restate schema text verbatim ('The password is not returned, logged, or emailed' duplicates the password field description; the idempotency sentence duplicates its schema description). The closing two sentences about 'this connection' and Connected apps are dense and slightly tangled, costing readability.

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 9-parameter open-world mutation with no output schema, the description covers the full lifecycle: preview, creation, emailed code, blocking dependency on confirm_platform_email, idempotency, and post-call account-listing recovery. An agent has everything needed to call it correctly and to handle the common result states.

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?

Schema coverage is only 44%, so the description has to carry weight — and it does for the non-obvious parameters: confirm's preview semantics, password optionality and non-return, idempotency_key's repeat-result behavior, and the email collision case. The remaining undocumented parameters (company_name, first_name, last_name, phone_number) are self-describing and get no treatment, which is the only shortfall.

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?

The opening sentence gives a specific verb and resource ('Opens a swift_platform account') and defines the resource in domain terms ('the company that will own a white-label app'). It also draws negative boundaries ('does not create the people who will use the app'), which sharply limits scope. It stops short of naming any sibling such as create_business_account or create_platform_app, so disambiguation is left to inference.

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?

It states explicitly when the tool previews versus mutates ('Omitted confirm returns a preview and does not create the account. True creates the company'). It also gives concrete next-step routing that names a sibling: call get_account without an account to list them, then pass account by name, plus a fallback of adding from Connected apps. Both the when-to-use and the when-not conditions are stated.

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

All Widely 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.