Skip to main content
Glama
recallnet

Trading Simulator MCP Server

by recallnet

get_leaderboard

Retrieve competition rankings to track performance and compare results in the Trading Simulator.

Instructions

Get the competition leaderboard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
competitionIdNoOptional competition ID (if not provided, the active competition is used)

Implementation Reference

  • src/index.ts:361-375 (registration)
    Registration of the 'get_leaderboard' tool in the TRADING_SIM_TOOLS array, including name, description, and input schema.
    {
      name: "get_leaderboard",
      description: "Get the competition leaderboard",
      inputSchema: {
        type: "object",
        properties: {
          competitionId: {
            type: "string",
            description: "Optional competition ID (if not provided, the active competition is used)"
          }
        },
        additionalProperties: false,
        $schema: "http://json-schema.org/draft-07/schema#"
      }
    },
  • MCP tool handler for 'get_leaderboard' in the CallToolRequestSchema switch statement. Extracts competitionId from arguments and calls tradingClient.getLeaderboard().
    case "get_leaderboard": {
      const competitionId = "competitionId" in args ? args.competitionId as string : undefined;
      const response = await tradingClient.getLeaderboard(competitionId);
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        isError: false
      };
    }
  • Input schema definition for the 'get_leaderboard' tool, specifying optional competitionId parameter.
    inputSchema: {
      type: "object",
      properties: {
        competitionId: {
          type: "string",
          description: "Optional competition ID (if not provided, the active competition is used)"
        }
      },
      additionalProperties: false,
      $schema: "http://json-schema.org/draft-07/schema#"
  • Implementation of getLeaderboard method in TradingSimulatorClient class, which makes the actual API request to /api/competition/leaderboard.
    async getLeaderboard(competitionId?: string): Promise<LeaderboardResponse | ErrorResponse> {
      let query = '';
      if (competitionId) {
        query = `?competitionId=${encodeURIComponent(competitionId)}`;
      }
      
      return this.request<LeaderboardResponse>(
        'GET', 
        `/api/competition/leaderboard${query}`,
        null,
        'get leaderboard'
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get' implying a read operation, but doesn't disclose behavioral traits such as whether it requires authentication, has rate limits, returns paginated results, or what happens if no competition is active. This leaves significant gaps for a tool that likely involves data retrieval.

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 extremely concise with a single sentence, 'Get the competition leaderboard', which is front-loaded and wastes no words. It efficiently conveys the core purpose without unnecessary elaboration, making it easy to scan and understand 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 complexity of a leaderboard tool (likely involving rankings, scores, or participants), no annotations, and no output schema, the description is incomplete. It doesn't explain what the leaderboard contains, how results are structured, or any behavioral aspects like error handling. This leaves the agent with insufficient information for reliable use.

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?

The input schema has 100% description coverage, with the parameter 'competitionId' documented as optional and defaulting to the active competition. The description adds no additional meaning beyond this, as it doesn't mention parameters at all. With high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter semantics.

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 the competition leaderboard' clearly states the action (get) and resource (competition leaderboard), but it's somewhat vague about what 'leaderboard' entails (e.g., rankings, scores, participants). It distinguishes from siblings like 'get_competition_status' or 'get_competition_rules' by focusing on rankings, but lacks specificity on scope or format.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if this is for active competitions only, how it relates to 'get_competition_status' or 'get_portfolio', or any prerequisites. The description alone offers no usage context beyond the basic purpose.

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