Skip to main content
Glama

Tokenbooks - crypto and fiat accounting and payments

Add Wallet(s) to Portfolio

add_wallet

Add one or more blockchain addresses and start their first sync. Omit the blockchain connection identifier (integrationId) to add an EVM 0x address on every supported EVM network; other addresses require an integrationId. It does not configure exchange accounts and reports which addresses were added or skipped.

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": {
      "workspaceRef": "<workspaceRef>",
      "portfolioRef": "<portfolioRef>",
      "wallets": "<wallets>"
    },
    "name": "add_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletsYes
portfolioRefYesPortfolio name or slug inside that workspace. Call list_portfolios to resolve it.
workspaceRefYesWorkspace name or slug. Call list_workspaces to resolve it.

Output Schema

NameRequiredDescriptionDefault
resultsYes
syncQueuedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / portfolioRef / description
      Previous value: -"Portfolio name or slug inside that workspace. Call list_portfolios, or find_portfolios when the user named one, to resolve it."New value: +"Portfolio name or slug inside that workspace. Call list_portfolios to resolve it."
    • changedInput schema / properties / workspaceRef / description
      Previous value: -"Workspace name or slug. Call list_workspaces, or find_workspaces when the user named one, to resolve it."New value: +"Workspace name or slug. Call list_workspaces to resolve it."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "results": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "address": {
      +            "type": "string"
      +          },
      +          "chainRef": {
      +            "type": "string"
      +          },
      +          "reason": {
      +            "type": "string"
      +          },
      +          "status": {
      +            "enum": [
      +              "created",
      +              "skipped"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "address",
      +          "status"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "syncQueued": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "results",
      +    "syncQueued"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / portfolioRef / description
      Added value: +"Portfolio name or slug inside that workspace. Call list_portfolios, or find_portfolios when the user named one, to resolve it."
    • addedInput schema / properties / workspaceRef / description
      Added value: +"Workspace name or slug. Call list_workspaces, or find_workspaces when the user named one, to resolve it."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive, so the safety bar is partly covered. The description adds real behavior beyond that: the call triggers a first sync, it is scoped to blockchain addresses only (not exchange accounts), and it returns a partial-success outcome listing added vs skipped addresses. It does not mention the 50-address batch ceiling or the effect of re-adding an existing address, which would matter for a non-idempotent write.

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 taut sentences with no filler: the action and sync side effect lead, the integrationId rule follows, and the exclusion plus return shape close. Each clause carries a distinct decision-relevant fact.

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 3-parameter write tool with an output schema, the description covers the pieces an agent could get wrong: required refs (pointed at resolvers in the schema), the integrationId fan-out rule, the exchange-account exclusion, and the partial-success return. Return-value detail is correctly left to the output schema.

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 67% and the description meaningfully adds to integrationId semantics — specifically what omitting it does (fan-out to every supported EVM network), which the schema's "use 'evm'" note does not state directly. workspaceRef, portfolioRef, and the per-wallet fields (name, address) get no treatment in the description, relying entirely on the schema text.

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+resource ("Add one or more blockchain addresses") plus an immediate side effect ("start their first sync"). It also draws an explicit boundary against a confusable operation — "does not configure exchange accounts" — so an agent can separate it from exchange-account flows without inspecting schemas.

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?

Gives a concrete conditional rule: omit integrationId for EVM 0x addresses across all supported EVM networks, but other address types require an integrationId. It also states an exclusion (exchange accounts) and, via the schema, points to list_workspaces/list_portfolios for ref resolution. It stops short of naming a sibling alternative (e.g. list_wallets or a sync tool) for the case where the address already exists.

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