Skip to main content
Glama

get_land

Retrieve detailed information for specific Axie Infinity land plots using grid coordinates to access ownership, terrain, and plot data.

Instructions

Get details for a specific land plot by its grid coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colYesColumn coordinate of the land plot.
rowYesRow coordinate of the land plot.

Implementation Reference

  • Handler implementation for the get_land tool, including input schema validation and GraphQL query execution.
    case "get_land": {
      const schema = z.object({
        col: z.coerce.number().int(),
        row: z.coerce.number().int(),
      });
      const { col, row } = schema.parse(args);
      const data = await client.query<{ land: unknown }>(queries.GET_LAND, {
        col,
        row,
      });
      return jsonContent(data.land);
    }
  • GraphQL query definition for retrieving land data.
    export const GET_LAND = `
      query GetLand($col: Int!, $row: Int!) {
        land(col: $col, row: $row) {
          tokenId
          owner
          col
          row
          landType
          minPrice
          order {
            id
            currentPrice
            currentPriceUsd
            paymentToken
            status
          }
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 states the tool retrieves details but does not specify whether it's a read-only operation, potential error conditions, rate limits, or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent 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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what details are returned, error handling, or usage constraints. For a tool with no structured behavioral data, more context is needed to fully understand its operation and results.

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?

The input schema has 100% description coverage, with clear documentation for 'col' and 'row' parameters. The description adds minimal value beyond the schema by implying these coordinates are used to identify a land plot, but it does not provide additional context like coordinate ranges or examples. Baseline 3 is appropriate as 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 tool's purpose: 'Get details for a specific land plot by its grid coordinates.' It specifies the verb ('Get details'), resource ('land plot'), and method ('by its grid coordinates'). However, it does not explicitly differentiate from sibling tools like 'search_lands', which might be used for broader queries, leaving room for improvement.

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 lacks any mention of prerequisites, exclusions, or comparisons to sibling tools such as 'search_lands', which could be used for different types of land queries. This omission reduces its effectiveness in helping an agent choose correctly.

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