Skip to main content
Glama

Spawn an agent

spawn_agent

Onboard a new AI agent in one step: Solana and EVM wallets it controls, $1.00 of Toolbooth credit, an ERC-8004 identity on Base, .toolbooth.eth, and MCP config. Pass the new agent's solanaAddress, evmAddress, apiKeyHash (hex SHA-256 of a fresh tb_live_ key you generated) and proofs: sign "toolbooth.io spawn_agent\nname:\nsolana:\nevm:\nkey:\nissued:" with the Solana key (Ed25519, base64 → solanaSig) and the EVM key (EIP-191 personal_sign, hex → evmSig). Or set generateKeys=true to receive new keys once in the result (discouraged: secrets pass through this conversation). Costs $2.00 USDC per call.

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": {
      "name": "<name>"
    },
    "name": "spawn_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name, 5-20 chars [a-z0-9-] → <name>.toolbooth.eth
evmSigNo
endpointNoOptional https endpoint for the agent (e.g. its MCP server)
issuedAtNo
solanaSigNo
apiKeyHashNoHex SHA-256 of the agent's new tb_live_ API key
evmAddressNo
descriptionNoPublic one-line description of the agent
generateKeysNoHave Toolbooth generate the keys and return them once (discouraged)
solanaAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=false/openWorldHint=true: states the $2.00 USDC per-call cost, the exact artifacts created (funded wallets, credit, on-chain identity, ENS subdomain), and the one-time secret-reveal risk of generateKeys. That cost and side-effect disclosure is precisely the context annotations cannot convey.

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 the outcome, and the literal signing string is necessary payload rather than filler. The middle sentence is long and dense with nested clauses, which costs some readability, but no sentence is removable.

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 costly, non-idempotent, world-touching mutation with no output schema, it covers cost, inputs, and the generateKeys return behavior. It omits what the normal (signed) response contains and what happens on duplicate/invalid name or failed signature verification, which an agent would want before paying $2.00.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 50% schema coverage, the description defines the semantics of the uncovered params: the exact canonical message to sign, base64 Ed25519 → solanaSig, EIP-191 personal_sign hex → evmSig, and the lowercase evm address requirement. This is meaning an agent could not infer from the bare schema types.

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?

Specific verb plus resource with enumerated concrete outcomes: wallets, $1.00 credit, ERC-8004 identity, <name>.toolbooth.eth, MCP config. It is unmistakably different from every sibling (all market-data/analysis tools), so an agent can pick it without opening the schema.

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?

Explains the two invocation paths (pre-signed proof vs generateKeys=true) and explicitly discourages the latter with a reason. No sibling alternatives exist to disambiguate against, but the description never says when spawning is appropriate versus unnecessary, so it stops short of a 5.

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.

Resources