Skip to main content
Glama

get_portfolio_wallet_endpoints

Retrieve endpoints for tracking wallet balances, transaction history, portfolio positions, and NFT holdings across protocols and chains. Enable financial auditing, multi-token analysis, and real-time monitoring for comprehensive wallet activity insights.

Instructions

Get all endpoints in the "Portfolio & Wallet" category. Endpoints for tracking user wallet balances, transaction history, portfolio positions across protocols and chains, net asset calculations, token holdings analysis, comprehensive wallet activity monitoring, real-time balance tracking, balance update history over time, multi-token portfolio analysis, balance changes with transaction context, financial auditing capabilities for individual users and addresses, wallet filtering and discovery, and NFT holdings tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the dynamic category tool 'get_portfolio_wallet_endpoints'. It calls getAllToolsInCategory to retrieve tools in 'Portfolio & Wallet' category and formats them into a response using asTextContentResult.
      handler: async (
        args: Record<string, unknown> | undefined,
      ): Promise<any> => {
        const toolsInCategory = getAllToolsInCategory(category.category);
        
        return asTextContentResult({
          category: category.category,
          description: category.description,
          tools: toolsInCategory.map((tool ) => ({
            name: tool.name,
            description: tool.description
          })),
        });
      },
    };
  • Tool metadata and input schema (empty object) for the dynamic category tool 'get_portfolio_wallet_endpoints'.
    tool: {
      name: categoryEndpointName,
      description: `Get all endpoints in the "${category.category}" category. ${category.description}`,
      inputSchema: zodToInputSchema(categorySchema),
    },
  • Registry entry defining the 'get_portfolio_wallet_endpoints' category name, description, and list of tools used to populate the tool response.
    {
      "category": "Portfolio & Wallet",
      "name": "get_portfolio_wallet_endpoints",
      "description": "Endpoints for tracking user wallet balances, transaction history, portfolio positions across protocols and chains, net asset calculations, token holdings analysis, comprehensive wallet activity monitoring, real-time balance tracking, balance update history over time, multi-token portfolio analysis, balance changes with transaction context, financial auditing capabilities for individual users and addresses, wallet filtering and discovery, and NFT holdings tracking.",
      "tools": [
        "user_history",
        "user_total_balance", 
        "user_token_balances",
        "get_user_protocol",
        "get_detailed_protocol_list",
        "get_detailed_protocol_list_on_all_chain",
        "fetch_wallet_balances",
        "fetch_wallet_token_activity",
        "wallets_search_filter",
        "token_wallets_filter",
        "wallet_detailed_stats",
        "wallet_chart_data",
        "wallet_nft_collections_data",
        "wallet_collection_assets"
      ]
    },
  • Helper function that matches tools from supportedTools against the category's tool list to provide the data for the handler.
    export function getAllToolsInCategory(category: string){
      let categoryUsed = ToolRegistry.find(tool => tool.category === category);
      if(!categoryUsed){
        return []
      }
      const allWrappedTools = supportedTools
      // return all the tools from wrapped tools that are in the category (name match)
      let toolsInCategory = [];
      for (const tool of categoryUsed.tools){
        const wrappedTool = allWrappedTools.find(wrappedTool => wrappedTool.name === tool);
        if(wrappedTool){
          toolsInCategory.push(wrappedTool);
        }
        else console.log(`Tool ${tool} not found in wrapped tools`);
      }
      return toolsInCategory;
    }
  • Registration of all dynamic category tools, including 'get_portfolio_wallet_endpoints', into the tools array returned by dynamicTools function used by the MCP server.
    return [getEndpointTool, callEndpointTool, ...categoryTools];
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool 'Get all endpoints', implying a read-only operation, but does not disclose behavioral traits such as rate limits, authentication needs, or what the output format looks like. The list of functionalities (e.g., 'real-time balance tracking') describes the endpoints' purposes, not the tool's behavior, leaving gaps in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose and lacks front-loading. The first sentence states the purpose, but the rest is a long, unstructured list of endpoint functionalities (e.g., 'comprehensive wallet activity monitoring', 'financial auditing capabilities') that does not earn its place by adding value beyond the initial statement. This reduces clarity and efficiency.

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

Completeness2/5

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

Given the complexity of endpoints and lack of annotations or output schema, the description is incomplete. It lists what the endpoints do but fails to explain the tool's behavior, return values, or usage context. For a tool that retrieves a category of endpoints, more details on output format or integration with siblings would be necessary for adequate completeness.

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 has 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and the endpoints' functionalities. This aligns with the baseline of 4 for tools with no parameters, as it adds context without redundancy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get all endpoints in the "Portfolio & Wallet" category.' It specifies the verb ('Get') and resource ('endpoints'), and distinguishes the category from siblings like 'get_defi_protocol_endpoints' or 'get_nft_analytics_endpoints'. However, it does not explicitly differentiate from all siblings, such as 'get_api_endpoint_schema', which might be related but serves a different function.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It lists functionalities like 'tracking user wallet balances' and 'transaction history', but does not specify prerequisites, exclusions, or compare it to sibling tools. For example, it does not clarify if this is for listing endpoints versus calling them, unlike 'call_api_endpoint'.

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/hive-intel/hive-crypto-mcp'

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