3dassets

Create account

create_account

Create a contributor account with just a username and email. A 6-digit verification code is sent by email; enter it to get your API key.

Instructions

Create a contributor account for the user. Needs only a username and email. There is no password anywhere in this product, so never ask the user for one. A 6-digit code is emailed to them; ask the user to read it to you, then call verify_account to receive their API key. Only do this with the user’s explicit consent.

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": {
      "email": "<email>",
      "username": "<username>"
    },
    "name": "create_account"
  }
}

Input Schema

Name	Required	Description
`name`	No	Optional display name shown on assets; defaults to the username
`email`	Yes
`website`	No
`username`	Yes	Public handle, lowercase letters/numbers/hyphens

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the email verification code flow, the absence of passwords, the need for consent, and the fact that the API key comes from verify_account rather than this tool. It still leaves some edge behaviors (e.g., duplicate email handling, code expiry) unstated, but the core side effects are clear.

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?

Four short sentences with no filler; purpose is front-loaded, followed by the most decision-relevant warnings and the next-step pointer. Every sentence earns its place.

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?

For a mutation with no annotations or output schema, the description covers the essential workflow: required fields, emailed code, user consent, and verify_account for the API key. It could be more complete by addressing duplicate accounts or what this call returns, but the agent has enough to invoke it correctly.

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 coverage is 50%, and the description adds some semantics by stating that only username and email are required and that no password field exists. However, it does not explain the optional name/website parameters beyond what the schema already says, so it only partially compensates for the coverage gap.

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 action ('Create a contributor account for the user') with a clear resource, and positions itself against verify_account by explaining that create_account is the first step and verify_account retrieves the API key. The no-password note further removes ambiguity about what this tool is for.

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 explicit when-to-use context: create only with the user's explicit consent, and only a username/email are needed. It also gives a when-not rule ('never ask the user for a password') and names verify_account as the required follow-up, so the agent knows the exact sequence.

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