Skip to main content
Glama

search_axies

Search Axie Infinity marketplace listings with filters for class, parts, breed count, auction type, and owner to find specific digital creatures.

Instructions

Search for Axies on the marketplace with optional filters. Supports filtering by class, parts, breed count, auction type, and owner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auctionTypeNoFilter by listing status. Defaults to All.
ownerNoFilter by owner Ronin address (ronin:xxxx or 0x...).
fromNoPagination offset. Default 0.
sizeNoNumber of results to return (max 100). Default 10.
sortNoSort order for results.
classesNoFilter by Axie classes.
partsNoFilter by part IDs (e.g. ['eyes-zeal', 'mouth-tiny-turtle']).
breedCountNoFilter by breed count values (e.g. [0, 1, 2]).
stagesNoFilter by stage values.
numMysticNoFilter by number of mystic parts.

Implementation Reference

  • The handler for 'search_axies' parses input arguments, builds a GraphQL query criteria object, and executes the search using the GraphQL client.
    // ── search_axies ─────────────────────────────────────────────────────
    case "search_axies": {
      const schema = z.object({
        auctionType: AuctionTypeEnum.optional(),
        owner: RoninAddress.optional(),
        from: z.coerce.number().int().min(0).default(0),
        size: z.coerce.number().int().min(1).max(100).default(10),
        sort: SortByEnum.optional(),
        classes: jsonArray(z.array(AxieClassEnum)).optional(),
        parts: jsonArray(z.array(PartId).max(6)).optional(),
        breedCount: jsonArray(z.array(z.coerce.number().int())).optional(),
        stages: jsonArray(z.array(z.coerce.number().int())).optional(),
        numMystic: jsonArray(z.array(z.coerce.number().int())).optional(),
      });
      const parsed = schema.parse(args ?? {});
    
      // Build the criteria object only when filter params are provided
      const criteria: Record<string, unknown> = {};
      if (parsed.classes && parsed.classes.length > 0) {
        criteria.classes = parsed.classes;
      }
      if (parsed.parts && parsed.parts.length > 0) {
        criteria.parts = parsed.parts;
      }
      if (parsed.breedCount && parsed.breedCount.length > 0) {
        criteria.breedCount = parsed.breedCount;
      }
      if (parsed.stages && parsed.stages.length > 0) {
        criteria.stages = parsed.stages;
      }
      if (parsed.numMystic && parsed.numMystic.length > 0) {
        criteria.numMystic = parsed.numMystic;
      }
    
      const variables: Record<string, unknown> = {
        from: parsed.from,
        size: parsed.size,
      };
      if (parsed.auctionType) variables.auctionType = parsed.auctionType;
      if (parsed.owner) variables.owner = parsed.owner;
      if (parsed.sort) variables.sort = parsed.sort;
      if (Object.keys(criteria).length > 0) variables.criteria = criteria;
    
      const data = await client.query<{ axies: unknown }>(
        queries.SEARCH_AXIES,
        variables
      );
      return jsonContent(data.axies);
    }
  • The tool definition for 'search_axies', including its input schema parameters for filtering Axies.
      name: "search_axies",
      description:
        "Search for Axies on the marketplace with optional filters. Supports filtering by class, parts, breed count, auction type, and owner.",
      inputSchema: {
        type: "object",
        properties: {
          auctionType: {
            type: "string",
            enum: ["All", "Sale", "NotForSale"],
            description: "Filter by listing status. Defaults to All.",
          },
          owner: {
            type: "string",
            description: "Filter by owner Ronin address (ronin:xxxx or 0x...).",
          },
          from: {
            type: "number",
            description: "Pagination offset. Default 0.",
          },
          size: {
            type: "number",
            description: "Number of results to return (max 100). Default 10.",
          },
          sort: {
            type: "string",
            enum: ["IdAsc", "IdDesc", "PriceAsc", "PriceDesc", "Latest", "LevelAsc", "LevelDesc"],
            description: "Sort order for results.",
          },
          classes: {
            type: "array",
            items: {
              type: "string",
              enum: ["Beast", "Aquatic", "Plant", "Bug", "Bird", "Reptile", "Mech", "Dawn", "Dusk"],
            },
            description: "Filter by Axie classes.",
          },
          parts: {
            type: "array",
            items: { type: "string" },
            description: "Filter by part IDs (e.g. ['eyes-zeal', 'mouth-tiny-turtle']).",
          },
          breedCount: {
            type: "array",
            items: { type: "number" },
            description: "Filter by breed count values (e.g. [0, 1, 2]).",
          },
          stages: {
            type: "array",
            items: { type: "number" },
            description: "Filter by stage values.",
          },
          numMystic: {
            type: "array",
            items: { type: "number" },
            description: "Filter by number of mystic parts.",
          },
        },
        required: [],
      },
    },
  • The GraphQL query definition for 'SearchAxies'.
    export const SEARCH_AXIES = `
      query SearchAxies(
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 mentions 'optional filters' and 'supports filtering' but doesn't disclose pagination behavior (beyond schema), rate limits, authentication requirements, error conditions, or what happens when no results match. For a search tool with 10 parameters, this leaves significant gaps in understanding how it behaves.

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, well-structured sentence that efficiently communicates the core functionality. Every word earns its place - it states the action, target, and key filter categories without redundancy or unnecessary elaboration. It's front-loaded with the essential information.

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?

For a search tool with 10 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns (list of Axies? metadata? paginated results?), doesn't mention performance characteristics or limitations, and provides no context about the marketplace environment. The agent would need to guess about the response format and operational constraints.

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 the schema already documents all 10 parameters thoroughly. The description adds marginal value by listing filter categories (class, parts, breed count, auction type, owner) but doesn't provide additional syntax, format details, or usage examples beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the verb ('Search') and resource ('Axies on the marketplace'), specifies the domain (marketplace search), and distinguishes from siblings like get_axie (single Axie retrieval) or search_lands (different resource type). It's specific and immediately tells what the tool does.

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 when to choose search_axies over get_axie for single Axie retrieval, or when to use it versus get_market_stats for aggregated data. There's no context about prerequisites, typical use cases, or limitations.

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