Skip to main content
Glama
recallnet

Trading Simulator MCP Server

by recallnet

get_portfolio

Retrieve current portfolio holdings and performance data for your trading team in the simulation environment.

Instructions

Get portfolio information for your team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP CallToolRequest handler case for 'get_portfolio': calls tradingClient.getPortfolio() and returns formatted text response.
    case "get_portfolio": {
      const response = await tradingClient.getPortfolio();
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        isError: false
      };
    }
  • TradingSimulatorClient.getPortfolio(): performs authenticated HTTP GET to backend /api/account/portfolio endpoint.
    async getPortfolio(): Promise<PortfolioResponse | ErrorResponse> {
      return this.request<PortfolioResponse>(
        'GET', 
        '/api/account/portfolio',
        null,
        'get portfolio'
      );
    }
  • src/index.ts:120-129 (registration)
    Tool registration in TRADING_SIM_TOOLS array (returned by ListToolsRequest): name, description, empty input schema.
    {
      name: "get_portfolio",
      description: "Get portfolio information for your team",
      inputSchema: {
        type: "object",
        properties: {},
        additionalProperties: false,
        $schema: "http://json-schema.org/draft-07/schema#"
      }
    },
  • Output type definitions: TokenPortfolioItem and PortfolioResponse (extends ApiResponse).
    export interface TokenPortfolioItem {
      token: string;
      amount: number;
      price: number;
      value: number;
      chain: BlockchainType;
      specificChain: SpecificChain | null;
    }
    
    export interface PortfolioResponse extends ApiResponse {
      teamId: string;
      totalValue: number;
      tokens: TokenPortfolioItem[];
      snapshotTime: string;
      source: PortfolioSource;
    }
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 implies a read operation ('Get'), but doesn't disclose behavioral traits such as authentication needs, rate limits, data freshness, or what 'portfolio information' entails (e.g., format, scope). This leaves significant gaps for an agent.

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 is a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 tool's simplicity (0 parameters, no output schema), the description is minimal but insufficient. It lacks details on what 'portfolio information' includes, how it's structured, or any behavioral context, which is needed for completeness even without complex schema elements.

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 tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for 0 parameters is 4, as the description doesn't need to compensate for missing param info, but it doesn't add extra value beyond stating the tool's purpose.

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

Purpose3/5

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

The description 'Get portfolio information for your team' states a clear verb ('Get') and resource ('portfolio information'), but it's vague about what specific information is retrieved (e.g., holdings, performance, allocations) and doesn't distinguish from siblings like 'get_balances' or 'get_trades'. It's adequate but lacks specificity.

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 like 'get_balances' or 'get_trades', nor does it mention any prerequisites or context for usage. It's a basic statement with no comparative or exclusionary information.

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/recallnet/trading-simulator-mcp'

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