Skip to main content
Glama

Set an agent identity

set_agent_profile
Idempotent

Use after your name is delivered to sign its agent profile, so other agents calling verify_agent see "verified: profile signed by current owner". Free (no Bitcoin transaction). Adds or edits the agent profile on a name you hold. Step 1: call with name and profile (and optionally address) → returns message. Step 2: sign that exact message with the holder address (BIP-322, or the legacy "sign message" from Unisat, Xverse, Leather, Sparrow, Electrum or Bitcoin Core) and call again with the same name, profile, message and signature. The message is valid for 1 hour. Only the current holder can set it.

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>",
      "profile": "<profile>"
    },
    "name": "set_agent_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe vanity name you hold.
addressNoHolder address (defaults to the current owner).
messageNoStep 2: the exact message returned in step 1.
profileYesAgent profile shown on the verify page and on proveitonchain.com/agent/<NAME>. Sign it later with set_agent_profile so it verifies.
signatureNoStep 2: base64 signature of message by the holder address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / profile / description
      Previous value: -"Agent identity shown as \"Agent identity\" on the verify page and on proveitonchain.com/agent/<NAME>."New value: +"Agent profile shown on the verify page and on proveitonchain.com/agent/<NAME>. Sign it later with set_agent_profile so it verifies."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the write, idempotent, non-destructive profile, so the description's added value is the operational context: a required sign-then-resubmit handshake, a 1-hour message validity window, and holder-only authorization. That is substantive beyond the structured hints, though it doesn't say what happens when the message expires mid-flow or how conflicts with an existing profile are resolved.

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 payoff ('verified: profile signed by current owner') before the mechanics, and the step numbering makes the two-phase flow scannable. Slightly redundant in restating the add/edit purpose after the sign rationale, but nearly every sentence carries information.

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 two-phase mutation with a nested profile object, no output schema, and five parameters, the description covers the return value (`message`), the signing formats and wallets accepted, the validity window, and the authorization constraint. Nothing an agent needs to complete the flow correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns a bump by explaining that step 1 takes name plus profile (optionally address) and step 2 must repeat the same name and profile alongside the returned message and signature. That sequencing constraint is real semantic guidance the schema fields alone don't enforce.

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 ('sign its agent profile', 'Adds or edits the agent profile on a name you hold') and ties the outcome to a named sibling ('other agents calling verify_agent see "verified: profile signed by current owner"'). An agent can distinguish this from get_agent_profile or verify_agent 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?

Gives an explicit trigger ('Use after your name is delivered'), a prerequisite ('Only the current holder can set it'), and a cost contrast ('Free (no Bitcoin transaction)') that separates it from on-chain siblings like broadcast or buy_name. The two-step call sequence removes any ambiguity about when to invoke it a second time.

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.