CryptoAd Network

Create an empty account

create_account

Idempotent

Creates an anonymous account with a zero balance and returns its API key, shown once. Only needed to upload an image before paying for anything (a Paid Visits ad needs one); otherwise use buy_ad_credit or create_ad, which create the account with the first payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_account"
  }
}

Input Schema

Name	Required	Description	Default
`idempotency_key`	No	Only to REPEAT an earlier call of this tool (a lost answer, a payment still confirming): the idempotency_key that call returned. Leave it out for a new call; the server then makes a random one and returns it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes beyond the annotations (readOnly=false, idempotent=true, destructive=false, openWorld=true) by disclosing that the account is anonymous with zero balance and that the returned API key is shown only once — a non-recoverable secret an agent must persist. It also flags the account is unpaying until credit is bought.

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?

Two tight sentences: the creation behavior and return value come first, then the conditional usage and alternatives. No filler, and the critical "shown once" warning is not buried.

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 one-parameter creation tool with no output schema, the description covers what is created, what is returned, the one-time secret risk, and the routing decision against siblings. Nothing an agent needs in order to call it correctly is missing; idempotency is fully handled by the schema.

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 single optional idempotency_key is fully documented there, including the repeat-call semantics. The description adds no parameter-level detail beyond the schema, so 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 ("Creates an anonymous account with a zero balance") and immediately distinguishes itself from the sibling paths that also create accounts (buy_ad_credit, create_ad). An agent can classify it without opening any schema.

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?

Explicitly names the only situation that requires it (uploading an image before paying, e.g. a Paid Visits ad) and names the alternatives to use otherwise, with the reason: they create the account as part of the first payment. When-to-use, when-not, and alternatives are all present.

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

All CryptoAd Network 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?