Skip to main content
Glama

Set username and visibility

set_profile
DestructiveIdempotent

Configure an account's username and choose whether trading counterparties see it and its track record, or keep the account anonymous. Pass a handle, a public flag, or both.

Instructions

Set this account's username and whether the accounts it trades with see it. An account is anonymous until it goes public. While it is public, every account it has a thread with — past deals included — sees its username and, beside it, its track record over ALL its swaps (deals, walk-aways, speed). Give either argument or both. handle_public: false hides both again and keeps the username; handle: null removes the username, makes the account anonymous and frees the name for anyone. A username can be set ten times an hour, attempts refused as taken included. whoami shows the current handle and handlePublic.

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": "set_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoUsername: 3 to 24 characters, the letters a to z, digits and _ (stored in lowercase). null removes it
handle_publicNotrue: counterparties see the username and the track record (needs a username). false: anonymous

Output Schema

NameRequiredDescriptionDefault
errorNoSet instead when the call failed
handleNoUsername; null = none
handlePublicNoCounterparties see the username and record

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.13.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint, idempotentHint, openWorldHint), the description discloses what actually gets exposed and to whom — every account with a thread, past deals included, sees the username plus track record over ALL swaps. It also discloses a concrete rate limit (ten attempts per hour, refusals counted) and the irreversibility nuance of freeing a name, which annotations alone 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?

The most important facts (what is set, anonymity default, either-or-both arguments) are front-loaded, and no sentence is filler. The long middle sentence about track record visibility is dense and slightly run-on, which costs a point but the content is not redundant.

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-parameter mutation with rich annotations and an output schema, the description covers visibility consequences, null/false edge cases, rate limits, and the read-path alternative. Nothing an agent needs to invoke it correctly appears to be 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, but the description adds meaning the schema lacks: that handle_public=false retains the stored username rather than clearing it, and that handle=null makes the account anonymous and releases the name to anyone. Those interaction rules between the two parameters are genuinely additive.

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 opening states a specific verb and resource: setting the account's username and whether counterparties see it. It also implicitly separates the write path from the read path by naming whoami as the tool that shows current handle/handlePublic, so an agent can distinguish it from that sibling.

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 explicitly says 'Give either argument or both', covering partial-update usage, and states the exact semantics of each option (false hides both but keeps the username; null removes the username and frees the name). It also routes reads to whoami, so when-to-use-this vs. when-to-use-the-alternative is fully covered.

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