Skip to main content
Glama

get_market_stats

Retrieve marketplace settlement statistics including transaction counts, Axie volumes, and trading data for the last 24 hours, 7 days, and 30 days.

Instructions

Get marketplace settlement statistics showing transaction counts, Axie counts, and volumes over the last 24 hours, 7 days, and 30 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for 'get_market_stats' tool which queries market statistics using the client.
    case "get_market_stats": {
      const data = await client.query<{ marketStats: unknown }>(
        queries.GET_MARKET_STATS
      );
      return jsonContent(data.marketStats);
    }
  • The GraphQL query definition for 'get_market_stats'.
    export const GET_MARKET_STATS = `
      query GetMarketStats {
        marketStats {
          last24Hours { count axieCount volume volumeUsd }
          last7Days { count axieCount volume volumeUsd }
          last30Days { count axieCount volume volumeUsd }
        }
      }
    `;
  • src/index.ts:244-250 (registration)
    Registration of the 'get_market_stats' tool.
    name: "get_market_stats",
    description:
      "Get marketplace settlement statistics showing transaction counts, Axie counts, and volumes over the last 24 hours, 7 days, and 30 days.",
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
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 of behavioral disclosure. It describes what data is retrieved but does not cover critical aspects like rate limits, authentication needs, data freshness, or error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operational behavior.

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 key action and details without any wasted words. It directly communicates the tool's function and scope, making it easy to parse and understand quickly.

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

Completeness3/5

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

Given the tool's complexity (retrieving statistical data over multiple timeframes) and lack of annotations and output schema, the description is minimally adequate. It specifies what data is fetched but does not explain the return format, structure, or units (e.g., currency for volumes). For a data-fetching tool with no structured output documentation, more detail would be helpful.

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 documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's output semantics (e.g., timeframes and data types). This meets the baseline for tools with no parameters.

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 with a specific verb ('Get') and resource ('marketplace settlement statistics'), including the types of data (transaction counts, Axie counts, volumes) and timeframes (24 hours, 7 days, 30 days). It distinguishes from siblings like 'get_overall_market_stats' by specifying 'settlement' statistics, though the distinction could be more explicit.

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. It does not mention prerequisites, compare with sibling tools like 'get_overall_market_stats', or specify scenarios where this tool is preferred. The description implies usage for historical settlement data but lacks explicit when/when-not instructions.

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