Skip to main content
Glama

get_leaderboard

Retrieve competitive rankings for Axie Infinity categories like AxieScore, LandPlot, or Runes to track player standings and performance metrics.

Instructions

Get leaderboard rankings for various competitive categories in Axie Infinity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesThe leaderboard category to retrieve.
fromNoPagination offset. Default 0.
sizeNoNumber of rankings to return. Default 10.

Implementation Reference

  • The handler implementation for the `get_leaderboard` tool inside the `CallToolRequestSchema` switch statement.
    case "get_leaderboard": {
      const schema = z.object({
        type: LeaderboardTypeEnum,
        from: z.coerce.number().int().min(0).default(0),
        size: z.coerce.number().int().min(1).max(100).default(10),
      });
      const parsed = schema.parse(args);
      const data = await client.query<{ leaderboard: unknown }>(
        queries.GET_LEADERBOARD,
        { type: parsed.type, from: parsed.from, size: parsed.size }
      );
      return jsonContent(data.leaderboard);
    }
  • The tool registration and schema definition for `get_leaderboard`.
    {
      name: "get_leaderboard",
      description:
        "Get leaderboard rankings for various competitive categories in Axie Infinity.",
      inputSchema: {
        type: "object",
        properties: {
          type: {
            type: "string",
            enum: ["AxieScore", "AxieCollector", "AxieOrigin", "AxieMystic", "AxieShiny", "AxieSummer", "AxieNightmare", "AxieJapan", "AxieXmas", "LandPlot", "LandSavannah", "LandForest", "LandArctic", "LandMystic", "LandGenesis", "Rune", "Charm", "Accessory", "WeeklyQuestPoints", "PremierQuestPoints"],
            description: "The leaderboard category to retrieve.",
          },
          from: {
            type: "number",
            description: "Pagination offset. Default 0.",
          },
          size: {
            type: "number",
            description: "Number of rankings to return. Default 10.",
          },
        },
        required: ["type"],
      },
    },
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 mentions retrieving rankings but doesn't disclose behavioral traits like rate limits, authentication requirements, pagination behavior beyond parameters, error conditions, or response format. The description is minimal and lacks operational context.

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 that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, resource, and domain context concisely.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the return values look like (e.g., structure of rankings), error handling, or operational constraints. For a tool with 3 parameters and competitive data, more context is needed for effective 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?

Schema description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional meaning beyond implying categories exist, which is already evident from the enum. Baseline score of 3 applies as the schema handles parameter semantics adequately.

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 action ('Get') and resource ('leaderboard rankings') with specific domain context ('for various competitive categories in Axie Infinity'). It distinguishes from most siblings that focus on individual assets or market data, though it doesn't explicitly contrast with similar ranking tools like 'get_top_sales'.

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. The description mentions 'various competitive categories' but doesn't specify which scenarios warrant this tool over sibling tools like 'get_top_sales' or 'get_market_stats' for ranking-related queries.

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/jackdlogan/axie-mcp'

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