Skip to main content
Glama

get_axie_equipment

Retrieve equipped items and accessories for specified Axies to analyze their current gear configuration and capabilities.

Instructions

Get the equipment and accessories currently equipped on one or more Axies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axieIdsYesList of Axie IDs to query equipment for (e.g. [1074, 1508]).

Implementation Reference

  • The handler implementation for "get_axie_equipment" in src/index.ts, which processes input arguments and queries the Axie API.
    case "get_axie_equipment": {
      const schema = z.object({
        axieIds: jsonArray(z.array(z.coerce.number().int())),
      });
      const { axieIds } = schema.parse(args);
      const data = await client.query<{ axiesEquipments: unknown }>(
        queries.GET_AXIE_EQUIPMENT,
        { axieIds }
      );
      return jsonContent(data.axiesEquipments);
    }
  • src/index.ts:436-451 (registration)
    The tool registration definition for "get_axie_equipment" in src/index.ts.
    {
      name: "get_axie_equipment",
      description:
        "Get the equipment and accessories currently equipped on one or more Axies.",
      inputSchema: {
        type: "object",
        properties: {
          axieIds: {
            type: "array",
            items: { type: "number" },
            description: "List of Axie IDs to query equipment for (e.g. [1074, 1508]).",
          },
        },
        required: ["axieIds"],
      },
    },
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 equipment, implying a read-only operation, but doesn't disclose any behavioral traits such as rate limits, authentication needs, data freshness, error handling, or whether it supports pagination for large lists of Axie IDs. This is a significant gap for a tool with no annotation coverage.

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, clear sentence that efficiently conveys the tool's purpose without any wasted words. It is front-loaded with the core action and resource, making it easy to parse. This is an excellent example of conciseness, as every part of the sentence earns its place in defining what the tool does.

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 moderate complexity (one required parameter) and lack of annotations and output schema, the description is minimally adequate. It states what the tool does but lacks details on behavior, usage context, and return values. Without an output schema, the description doesn't explain what the equipment data looks like (e.g., format, fields), leaving gaps that could hinder an agent's ability to use the tool effectively.

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 the 'axieIds' parameter fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (e.g., it doesn't explain format constraints, valid ID ranges, or handling of invalid IDs). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 the equipment and accessories currently equipped on one or more Axies.' It specifies the verb ('Get'), resource ('equipment and accessories'), and scope ('on one or more Axies'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_axie' (which might return general Axie data) or 'get_erc1155_tokens' (which might include equipment tokens), so it doesn't reach the highest 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or specific contexts for usage. For example, it doesn't clarify if this is for real-time data or cached information, or how it relates to tools like 'get_axie' or 'get_erc1155_tokens'. This lack of usage context leaves the agent to infer when this tool is appropriate.

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