Skip to main content
Glama

menese_portfolio

Retrieve your complete cryptocurrency portfolio across 19 blockchains including EVM, Solana, Bitcoin, and ICP ecosystem tokens with a configured wallet.

Instructions

Get your full portfolio across all 19 supported blockchains (EVM, Solana, Bitcoin, ICP, etc.) plus ICP ecosystem tokens (ckBTC, ckETH, ckUSDC). Requires a configured wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the menese_portfolio tool, which retrieves portfolio data across multiple chains and ICP ecosystem tokens.
    async () => {
      const identity = store.get();
      if (!identity) {
        return { content: [{ type: "text" as const, text: "No wallet configured. Use menese_setup first." }], isError: true };
      }
    
      const portfolio = await cacheFetch(
        CacheKeys.portfolio(identity.principal),
        TTL.PORTFOLIO,
        async () => {
          const seedOrId = resolveActorIdentity(store);
          const [native, icrc1] = await Promise.all([
            getPortfolio(config, identity.principal, seedOrId),
            getAllICRC1Balances(config, seedOrId),
          ]);
          return { native, icrc1Tokens: icrc1 };
        },
      );
    
      const lines: string[] = [];
    
      // Native balances
      if (portfolio.native.ok) {
        const { data: balances, errors } = portfolio.native;
    
        if (balances.length > 0) {
          lines.push("## Portfolio Balances\n");
          for (const b of balances) {
            lines.push(`- ${formatBalance(b)}`);
          }
        } else {
          lines.push("## Portfolio Balances\n");
          lines.push("No balances found across supported chains.");
        }
    
        // Categorize errors
        if (errors && errors.length > 0) {
          const subRequired = errors.filter(e => isSubscriptionError(e.error));
          const other = errors.filter(e => !isSubscriptionError(e.error));
    
          if (subRequired.length > 0) {
            const chains = subRequired.map(e => CHAIN_LABEL[e.chain] ?? e.chain).join(", ");
            lines.push(`\n## Subscription Required\n`);
            lines.push(`${chains} — balance queries require a Menese subscription.`);
            lines.push(`Upgrade at https://menese.io to unlock full multi-chain access.`);
          }
    
          if (other.length > 0) {
            lines.push(`\n## Unavailable Chains\n`);
            for (const e of other) {
              lines.push(`- ${CHAIN_LABEL[e.chain] ?? e.chain}: ${e.error}`);
            }
          }
        }
      } else {
        lines.push(`Portfolio fetch failed: ${portfolio.native.error}`);
      }
    
      // ICRC-1 tokens (ckBTC, ckETH, ckUSDC, etc.)
      if (Array.isArray(portfolio.icrc1Tokens) && portfolio.icrc1Tokens.length > 0) {
        lines.push(`\n## ICP Ecosystem Tokens\n`);
        for (const t of portfolio.icrc1Tokens) {
          lines.push(`- ${t.symbol}: ${t.balance}`);
        }
      }
    
      return {
        content: [{ type: "text" as const, text: lines.join("\n") }],
      };
    },
  • Registration of the menese_portfolio tool.
    server.registerTool(
      "menese_portfolio",
      {
        description:
          "Get your full portfolio across all 19 supported blockchains (EVM, Solana, Bitcoin, ICP, etc.) " +
          "plus ICP ecosystem tokens (ckBTC, ckETH, ckUSDC). Requires a configured wallet.",
        inputSchema: {},
      },
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully communicates the broad scope (19 chains) and the wallet dependency, but omits critical behavioral details such as whether data is real-time or cached, rate limiting, specific error scenarios, or the structure/format of the returned portfolio data.

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 description consists of exactly two high-value sentences. The first front-loads the action and comprehensive scope (19 chains, specific tokens), while the second states the critical prerequisite. No filler words or redundant phrases are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of both annotations and an output schema, and considering the complexity of aggregating 19 blockchains, the description is minimally adequate but incomplete. It lacks details about the return value structure (balances, USD values, token metadata) and does not explicitly differentiate from menese_balance, which is important for sibling tool selection.

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?

The input schema contains zero parameters (empty object). Per evaluation guidelines, this establishes a baseline score of 4. The description appropriately does not invent parameter semantics where none exist.

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 uses a specific verb ('Get') and resource ('full portfolio') and clearly defines scope ('across all 19 supported blockchains' plus specific ICP ecosystem tokens). The comprehensive scope distinguishes it from siblings like menese_balance (likely single-chain/account) and menese_prices (market data vs holdings).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description provides a clear prerequisite ('Requires a configured wallet'), indicating when the tool is usable. However, it lacks explicit guidance on when to use this versus menese_balance or other siblings, and does not mention error conditions (e.g., what happens if no wallet is configured).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Aboodtt404/mcp-menese-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server