Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

identity_register

Register a real wallet identity by submitting a wallet address, fresh nonce, and ECDSA signature; the tool records the identity and never signs for you.

Instructions

[Wicked Identity] Register a REAL wallet (no stake required). Needs your signature over identity_get_nonce's message; this tool never signs. Sandbox identities are registered by identity_sandbox_register instead.

Use when you want a lightweight identity record for your wallet, with a signature over the nonce message. Not for proving you are an agent (use identity_get_challenge next).

Behavior: writes state upstream (not read-only); needs the credentials or wallet signature noted above where applicable.

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": {
      "wallet": "<wallet>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "identity_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYesNonce from a FRESH identity_get_nonce call.
walletYesYour 0x wallet address on Base, or the sandbox wallet from identity_sandbox_register.
signatureYes0x-prefixed ECDSA signature over that nonce's message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.2
    • changedInput schema / properties / wallet / description
      Previous value: -"Your agent's 0x wallet address on Base."New value: +"Your 0x wallet address on Base, or the sandbox wallet from identity_sandbox_register."
  2. First observedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful context beyond those annotations: it writes state upstream, requires a wallet signature over the nonce message, and this tool never signs on the user's behalf. It does not describe the response shape, but the safety/mutation profile is well covered.

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?

The description is front-loaded with the action, prerequisites, and alternatives. It is slightly verbose with the bracketed prefix and a final behavior sentence that partially repeats annotation information, but every part is relevant and no major waste is present.

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 tool with full schema coverage, rich annotations, and no output schema, the description gives enough operational context to call it correctly: prerequisites, non-signing behavior, alternatives, and upstream write behavior. It could be slightly more complete by noting what a successful registration returns or records, but that is a minor gap.

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%, and the schema documents wallet, nonce, and signature with formats. The description reinforces that the nonce should come from a fresh identity_get_nonce call and that the signature is over that nonce's message, but this largely repeats schema-level meaning. Baseline 3 is appropriate when the schema carries parameter semantics.

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?

The description states a specific verb and resource: register a REAL wallet as an identity. It explicitly distinguishes this from sandbox registration and from agent-challenge proving, so an agent can select it without opening sibling schemas.

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 gives explicit when-to-use guidance ('lightweight identity record for your wallet') and names alternatives: sandbox identities use identity_sandbox_register, and proving agent status uses identity_get_challenge. The prerequisite path through identity_get_nonce is also stated.

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