Skip to main content
Glama

get_axie

Retrieve detailed Axie information including stats, parts, abilities, genes, breeding data, listing price, and battle info using the Axie ID.

Instructions

Get detailed information about a single Axie by its ID, including stats, parts, abilities, genes, breeding info, current listing price, and battle info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axieIdYesThe numeric ID of the Axie (e.g. '1234567')

Implementation Reference

  • The handler logic for the 'get_axie' tool, which parses the axieId and queries the client.
    case "get_axie": {
      const schema = z.object({ axieId: AxieId });
      const { axieId } = schema.parse(args);
      const data = await client.query<{ axie: unknown }>(queries.GET_AXIE, {
        axieId,
      });
      return jsonContent(data.axie);
    }
  • src/index.ts:157-173 (registration)
    The tool definition/registration for 'get_axie' in the toolDefinitions array.
    {
      name: "get_axie",
      description:
        "Get detailed information about a single Axie by its ID, including stats, parts, abilities, genes, breeding info, current listing price, and battle info.",
      inputSchema: {
        type: "object",
        properties: {
          axieId: {
            type: "string",
            description: "The numeric ID of the Axie (e.g. '1234567')",
          },
        },
        required: ["axieId"],
      },
    },
    {
      name: "search_axies",
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 lists the types of information returned (stats, parts, etc.), which adds some context, but it doesn't cover critical aspects like error handling (e.g., what happens if the ID is invalid), rate limits, authentication needs, or data freshness. For a read operation with zero annotation coverage, this is a significant gap.

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 ('Get detailed information about a single Axie by its ID') and then enumerates the included data types without unnecessary elaboration. Every word earns its place, making it highly concise and well-structured.

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 low complexity (1 parameter, no nested objects) and high schema coverage, the description is adequate for basic use. However, with no annotations and no output schema, it lacks details on behavioral traits (e.g., error cases) and return format, which could hinder an agent's ability to handle edge cases effectively. It meets minimum viability but has clear gaps.

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 parameter 'axieId' clearly documented as a numeric ID. The description adds no additional semantic details beyond what the schema provides, such as format constraints or examples beyond the schema's 'e.g. '1234567''. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Get' and the resource 'detailed information about a single Axie by its ID', specifying exactly what the tool does. It distinguishes itself from siblings like 'search_axies' (which returns multiple results) and 'get_axie_children' (which focuses on offspring), making the purpose specific and well-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when detailed information about a specific Axie is needed, but it doesn't explicitly state when to use this tool versus alternatives like 'search_axies' for broader queries or 'get_axie_children' for related data. No exclusions or prerequisites are mentioned, leaving some ambiguity in context.

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