Skip to main content
Glama

search_lands

Find available land plots on the Axie Infinity marketplace using filters for owner, land type, auction status, and sorting options.

Instructions

Search for land plots on the Axie Infinity marketplace with optional filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerNoFilter by owner Ronin address (ronin:xxxx or 0x...).
landTypeNoFilter by land type.
fromNoPagination offset. Default 0.
sizeNoNumber of results to return. Default 10.
sortNoSort order for results.
auctionTypeNoFilter by listing status.

Implementation Reference

  • The handler function for the 'search_lands' tool, which parses input arguments, constructs GraphQL variables, and queries the client.
    case "search_lands": {
      const schema = z.object({
        owner: RoninAddress.optional(),
        landType: LandTypeEnum.optional(),
        from: z.coerce.number().int().min(0).default(0),
        size: z.coerce.number().int().min(1).max(100).default(10),
        sort: SortByEnum.optional(),
        auctionType: AuctionTypeEnum.optional(),
      });
      const parsed = schema.parse(args ?? {});
    
      const variables: Record<string, unknown> = {
        from: parsed.from,
        size: parsed.size,
      };
      if (parsed.auctionType) variables.auctionType = parsed.auctionType;
      if (parsed.sort) variables.sort = parsed.sort;
      if (parsed.owner) {
        variables.owner = {
          address: parsed.owner,
          ownerships: ["Owned"],
        };
      }
      if (parsed.landType) {
        variables.criteria = { landType: [parsed.landType] };
      }
    
      const data = await client.query<{ lands: unknown }>(
        queries.GET_LANDS,
        variables
      );
      return jsonContent(data.lands);
    }
  • src/index.ts:303-320 (registration)
    Tool definition/registration for 'search_lands'.
    name: "search_lands",
    description:
      "Search for land plots on the Axie Infinity marketplace with optional filters.",
    inputSchema: {
      type: "object",
      properties: {
        owner: {
          type: "string",
          description: "Filter by owner Ronin address (ronin:xxxx or 0x...).",
        },
        landType: {
          type: "string",
          enum: ["Savannah", "Forest", "Arctic", "Mystic", "Genesis", "LunaLanding"],
          description: "Filter by land type.",
        },
        from: {
          type: "number",
          description: "Pagination offset. Default 0.",
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions searching with filters but doesn't describe what the search returns (e.g., list of lands with details), pagination behavior (implied by 'from' and 'size' but not explained), rate limits, authentication needs, or error conditions. This is inadequate for a search tool with multiple parameters.

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 ('Search for land plots') and adds necessary context ('on the Axie Infinity marketplace with optional filters'). There's zero wasted verbiage, making it easy to parse 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?

For a search tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., structure of land plot data), how results are presented, or behavioral aspects like pagination limits. The agent would lack sufficient context to use this tool effectively without trial and error.

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 6 parameters thoroughly with descriptions and enums. The description adds no additional parameter semantics beyond mentioning 'optional filters', which is already implied by the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Search for land plots') and the target resource ('on the Axie Infinity marketplace'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its sibling 'get_land' or 'search_axies', which would be needed for a perfect score.

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 mentions 'optional filters' but provides no guidance on when to use this tool versus alternatives like 'get_land' or 'search_axies'. There's no context about use cases, prerequisites, or comparisons with sibling tools, leaving the agent without usage direction.

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