Skip to main content
Glama

Self-register a new Verifly account + API key

register_account

Programmatically create a brand-new Verifly account — this is how an agent self-onboards with no human in the loop. Requires only an email and a password (min 8 chars; disposable email domains are rejected). The new account starts with 100 immediately usable credits without inbox confirmation. Optional confirmed work-email proof unlocks 400 more, 500 total. The response includes the new account id/email and a freshly generated api_key.key that is shown ONCE — capture and store it immediately, it cannot be retrieved again. Subsequent tool calls can then use that key as the bearer token.

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>",
      "password": "<password>"
    },
    "name": "register_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail for the new account (not a disposable domain).
passwordYesPassword for the new account (minimum 8 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare it is a non-destructive, non-open-world write; the description adds substantial behavior: disposable domains rejected, 100 immediately usable credits with no inbox confirmation, 400 more with confirmed work email, and the critical one-time visibility of api_key.key. That last point is exactly the kind of irreversible behavior an agent cannot infer from annotations.

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?

Front-loaded with purpose, then constraints, then the return-value warning, so the most critical fact (one-time API key) lands before the reader stops. It is a bit long and repeats schema-stated constraints, which costs it the top score.

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?

No output schema exists, so the description carries the return contract and does so: account id/email plus api_key.key and how to use it as a bearer token. For a two-parameter registration tool this covers everything an agent needs to call it and act on the result.

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 100% and the description's parameter details (min 8 chars, disposable domain rejection) largely restate what the schema already documents. The added value is mostly sequencing guidance about the returned key rather than new parameter meaning, 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 ('Programmatically create a brand-new Verifly account') plus the agent-facing intent of self-onboarding. This is clearly distinguishable from read-oriented siblings like get_account or get_credits.

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?

Explicitly frames the scenario ('this is how an agent self-onboards with no human in the loop'), which tells the agent when this tool applies. It stops short of naming a sibling or stating when NOT to register (e.g. when a key already exists), so it is clear context without explicit alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.