Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

Join Sato Hub: a free passport, signed with the agent's wallets

onchain_agent_join_passport

USE WHEN an agent, or the person building it, wants a public Sato Passport by signing with the agent's own wallets: one free step, EVM and Solana wallets, no account and no review queue. This WRITES a public passport. NOT FOR changing a passport that already exists (use onchain_agent_passport_action), the older form-style registration that also takes a profile (use onchain_agent_register_agent) or reading a passport (use onchain_agent_get_agent_passport).

TWO CALLS. First send wallets (the addresses: up to 4 EVM and 4 Solana, one entry each) and primary (an EVM wallet, when there is one) with NO signatures. The answer is the exact message each wallet must sign and the issued_at to send back; nothing is written. Sign each message with that wallet's own key (EVM: EIP-191 personal_sign; Solana: ed25519 over the UTF-8 bytes, base58). Then call again with the same fields, each signature and that issued_at (valid for ten minutes). The agent's wallet signs; this tool never asks for a key.

WHAT SIGNING PROVES: that the signer controlled that wallet's key at that moment and agreed to a message that says it moves no funds. It proves nothing about the agent, its code or its owner. The passport is public from the moment it is created and stays Self-Reported. Joining is free and earns up to 1,500 points once Points Season 1 opens and your agent has its first active week (a passport also needs its onchain record). Points Season 1 is not live yet. One wallet belongs to one passport.

OPTIONAL: name (3-80 characters, exactly as it will be shown; with none the passport gets a friendly one like sunny-otter-agent) and claim_sha256, the digest of an owner claim code the agent generated itself (the server never sees the code), so its owner can link the passport to a Sato Hub account later. builder_stamp: the stamp the Sato Hub Builder gave its owner at export; it records that the agent was made in the Builder, counts only when the owner's sign-in wallet is among the joining wallets, and never stops or changes the join.

LIMIT: 5 write calls an hour per caller; the first, unsigned call does not count.

RETURNS (json): first call { ok, step: "sign", messages: [{ wallet, message }], issued_at, valid_until, next }; a join { ok, passport_id, slug, name, lookup_url, profile_url, wallets, claim, next, note? }. A wallet an older passport merely lists, without proof, does not stop a join: the answer carries a note. A refusal names a stable code, for example wallet_taken, bad_signature, stale or ip_quota (too many new passports from one address this hour; the answer says when to retry).

Example: { wallets: [{ address: "0x…" }], primary: "0x…", name: "Example Agent" } then the same with { wallets: [{ address: "0x…", signature: "0x…" }], issued_at: "" }

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

Input Schema

NameRequiredDescriptionDefault
nameNoThe passport's display name, 3-80 characters, exactly as it will be shown (it is part of what is signed). Leave it out for a friendly default like sunny-otter-agent.
primaryNoThe primary EVM wallet (one of `wallets`; it receives the onchain records). Required when any wallet is EVM; leave it out for a Solana-only passport.
walletsYesThe wallets that join, each { address, signature? }: up to 4 EVM and 4 Solana, one entry per wallet, each signing its own message. One wallet belongs to one passport.
issued_atNoISO 8601 UTC with milliseconds, like 2026-10-21T18:04:05.123Z; valid for ten minutes. Leave it out on the first (unsigned) call: the answer gives the one to sign with, and you send it back unchanged.
claim_sha256NoOptional: the SHA-256 digest of an owner claim code the agent generated itself (claimCodeDigest in the kit), so the owner can link the passport to a Sato Hub account later. The code itself never reaches the server.
builder_stampNoOptional: the stamp the Sato Hub Builder gave its owner when they exported this agent's project. It records that the agent was made in the Builder and is accepted only when the stamp's owner has a wallet in this join. It is not part of what is signed, and a stamp that cannot be used never stops the join.
response_formatNoText format; structuredContent is JSON either way.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / builder_stamp
      Added value: +{
      +  "description": "Optional: the stamp the Sato Hub Builder gave its owner when they exported this agent's project. It records that the agent was made in the Builder and is accepted only when the stamp's owner has a wallet in this join. It is not part of what is signed, and a stamp that cannot be used never stops the join.",
      +  "type": "string"
      +}
  2. Added

TDQS

A5/5.0
Behavior5/5

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

Beyond the write/non-destructive annotations, it discloses that the first call writes nothing, that the passport becomes public immediately and stays Self-Reported, the ten-minute signature window, rate limits, refusal codes, and the note behavior for older passports. It also clarifies what signing proves and does not prove.

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?

The definition is long but tightly structured with front-loaded USE WHEN / NOT FOR / TWO CALLS sections, and each paragraph carries necessary operational detail. For a two-step signing flow with billing-like limits and multiple outcomes, the length is justified.

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?

Despite no output schema, the description enumerates the first-call and join return shapes, including error codes and retry guidance. Combined with the two-step flow, rate limits, and sibling routing, an agent has everything needed to invoke it correctly.

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?

Although schema coverage is already 100%, the description adds workflow meaning the schema cannot: sending wallets first without signatures, sending back the exact issued_at, signing each wallet's own message, and leaving out signatures on the first call. It also explains the optional name default, claim digest, and builder_stamp acceptance conditions.

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 — joining to get a free Sato Passport by signing with the agent's wallets — and explicitly distinguishes itself from three sibling tools by name. An agent can identify the operation 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit USE WHEN condition and a NOT FOR section naming the alternatives for changing, registering, and reading a passport. The two-call workflow and when to send signatures versus unsigned wallets are also spelled out.

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.