Skip to main content
Glama

get_top_sales

Retrieve highest-value sales data for Axie Infinity tokens within specified timeframes to analyze market trends and pricing.

Instructions

Get the top sales for a given token type (Axie, Land, Item, etc.) over a specified time period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenTypeYesThe type of token to get top sales for.
periodTypeYesThe time period to look back.
sizeNoNumber of top sales to return. Default 10.

Implementation Reference

  • The handler for the 'get_top_sales' tool, which parses arguments, executes the GraphQL query using the client, and returns the top sales data.
    case "get_top_sales": {
      const schema = z.object({
        tokenType: TokenTypeEnum,
        periodType: PeriodTypeEnum,
        size: z.coerce.number().int().min(1).max(100).default(10),
      });
      const parsed = schema.parse(args);
      const data = await client.query<{ topSales: unknown }>(
        queries.GET_TOP_SALES,
        {
          tokenType: parsed.tokenType,
          periodType: parsed.periodType,
          size: parsed.size,
        }
      );
      return jsonContent(data.topSales);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read-only operation but doesn't disclose rate limits, authentication needs, data freshness, pagination, error conditions, or what 'top sales' means (e.g., by volume, price, count). This is inadequate for a tool with potential complexity in sales 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.

Conciseness4/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. It avoids redundancy and wastes no words, though it could be slightly more structured by separating key elements like token types and period.

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 return values (e.g., format of sales data, fields included), error handling, or behavioral constraints. For a tool fetching potentially complex sales data, this leaves significant gaps for an AI agent to infer usage.

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 well-documented in the schema. The description adds marginal value by mentioning token types and time period, but doesn't explain semantics beyond what's in schema descriptions (e.g., what 'top' means, how 'size' interacts with defaults). Baseline 3 is appropriate given high schema coverage.

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 ('top sales for a given token type'), specifying the scope ('over a specified time period'). It distinguishes from most siblings by focusing on sales data rather than individual items or profiles, though it doesn't explicitly differentiate from 'get_market_stats' or 'get_overall_market_stats' which might have overlapping functionality.

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 doesn't mention sibling tools like 'get_market_stats' or 'get_overall_market_stats' that might serve similar purposes, nor does it specify prerequisites, exclusions, or contextual triggers for selecting this tool.

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