Skip to main content
Glama
Sign In
Anythink-MCP

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Sign up for Anythink

signup

Create a new Anythink platform account with first name, last name, email, and password. Use this before login when the user has no account; email confirmation may be required.

Instructions

Register a brand-new Anythink platform account with email and password. Use this only when the user has no account yet; if they already have one, use 'login' instead. This creates the top-level user identity — it does not create a billing account or project (do that with 'accounts_create' and 'projects_create' after logging in). On success the user may need to click an email confirmation link before 'login' works; tell them to confirm, then call 'login'.

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address — becomes the login identifier and must be unique
lastNameYesUser's last name
passwordYesPassword for the new account; choose a strong value
firstNameYesUser's first name
referralCodeNoOptional referral code, if the user was invited by another customer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.27
    • removedInput schema / description
      Removed value: -"Register a brand-new Anythink platform account with email and password. Use this only when the user has no account yet; if they already have one, use 'login' instead. This creates the top-level user identity — it does not create a billing account or project (do that with 'accounts_create' and 'projects_create' after logging in). On success the user may need to click an email confirmation link before 'login' works; tell them to confirm, then call 'login'."
    • changedInput schema / properties / referralCode / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"signup"
  2. Changed6 schema fields changedv0.2.21
    • changedInput schema / description
      Previous value: -"Create a new Anythink account"New value: +"Register a brand-new Anythink platform account with email and password. Use this only when the user has no account yet; if they already have one, use 'login' instead. This creates the top-level user identity — it does not create a billing account or project (do that with 'accounts_create' and 'projects_create' after logging in). On success the user may need to click an email confirmation link before 'login' works; tell them to confirm, then call 'login'."
    • changedInput schema / properties / email / description
      Previous value: -"Email address"New value: +"Email address — becomes the login identifier and must be unique"
    • changedInput schema / properties / firstName / description
      Previous value: -"First name"New value: +"User's first name"
    • changedInput schema / properties / lastName / description
      Previous value: -"Last name"New value: +"User's last name"
    • changedInput schema / properties / password / description
      Previous value: -"Password"New value: +"Password for the new account; choose a strong value"
    • changedInput schema / properties / referralCode / description
      Previous value: -"Referral code (optional)"New value: +"Optional referral code, if the user was invited by another customer"
  3. First observedv0.2.6

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare openWorldHint and destructiveHint=false, so the description adds real value: the email-confirmation prerequisite before 'login' works, and the explicit statement that it creates only the top-level user identity and not a billing account or project. It stops short of describing the return payload or uniqueness failure behavior, so a 4 rather than 5.

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?

Front-loads the core action, then immediately addresses the routing decision, the scope boundary, and the post-success step. Four sentences, each carrying distinct operational information with no 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?

For an unauthenticated, side-effecting call with no output schema, the description covers the critical success path (email confirmation) and the boundary with related tools. It does not describe what the call returns or error cases, which is a minor gap given the low overall complexity.

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%, so all five parameters, including the referralCode default and the email uniqueness constraint, are already documented. The description mentions email and password but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Register a brand-new Anythink platform account with email and password') and explicitly scopes it against the sibling 'login'. It also carves out what it is not, distinguishing it from 'accounts_create' and 'projects_create'.

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 condition for use ('only when the user has no account yet'), the negative condition with the alternative ('if they already have one, use login instead'), and names the follow-on tools for adjacent tasks. Nothing is left to inference.

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