Skip to main content
Glama
Sign In

Moonsox

by com.moonsox
OverviewDiscussionsAdmin

Link a Solana wallet on Trust

trust_link_wallet

Link your on-curve Solana wallet as the bot's stake wallet, with proof you control it (nonce + signature from trust_wallet_challenge). Desk pays this wallet and your bond belongs to it. Needed before a Desk loan or bond.

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": {
      "botId": "<botId>",
      "session": "<session>",
      "solanaPubkey": "<solanaPubkey>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "trust_link_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
botIdYes
nonceYesnonce from trust_wallet_challenge
sessionYesYour Trust session token (from trust_open_session). Used for this call only; never stored.
signatureYesWallet signature over the challenge message (base64 or base58)
solanaPubkeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / nonce
      Added value: +{
+  "description": "nonce from trust_wallet_challenge",
+  "maxLength": 256,
+  "minLength": 8,
+  "type": "string"
+}
    • addedInput schema / properties / signature
      Added value: +{
+  "description": "Wallet signature over the challenge message (base64 or base58)",
+  "maxLength": 128,
+  "minLength": 64,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "botId",
-  "session",
-  "solanaPubkey"
-]New value: +[
+  "botId",
+  "session",
+  "solanaPubkey",
+  "nonce",
+  "signature"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already disclose that this is a non-read-only, non-destructive, open-world operation. The description adds useful consequence context beyond annotations: the wallet becomes the bot's stake wallet, the Desk pays it, and the bond belongs to it, which is meaningful for a mutation operation.

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?

Three compact sentences with no wasted language. The core action is front-loaded, followed by consequence and prerequisite in a logical order.

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 five-parameter mutation with no output schema, the description covers purpose, proof requirements, consequences, and prerequisite usage well. It could say more about what happens on success or whether an existing linked wallet is replaced, but the essential call context is present.

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 coverage is 60%, so the schema already documents session, nonce, and signature fairly well. The description reinforces that nonce and signature come from trust_wallet_challenge and that the pubkey must be on-curve, but it adds little about botId or session semantics beyond what the structured fields already provide.

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?

Uses a specific verb and resource: linking an on-curve Solana wallet as the bot's stake wallet on Trust, with proof of control. The scope (stake wallet, bot, bond/loan context) distinguishes it from nearby siblings such as trust_wallet_challenge and trust_prove_wallet.

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?

Clearly states the prerequisite workflow (nonce + signature from trust_wallet_challenge) and the business condition ('Needed before a Desk loan or bond'). It does not explicitly name exclusions or alternatives, but the when-to-use context is strong.

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

All Moonsox toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources