Skip to main content
Glama

get_erc1155_tokens

Query ERC1155 tokens like runes, charms, and accessories in Axie Infinity, with options to filter by owner and token type for inventory management.

Instructions

Get ERC1155 tokens such as runes, charms, accessories, ingredients, and other in-game items, optionally filtered by owner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerNoFilter by owner Ronin address (ronin:xxxx or 0x...).
tokenTypeYesThe type of ERC1155 token to query.
fromNoPagination offset. Default 0.
sizeNoNumber of results to return. Default 10.

Implementation Reference

  • The handler implementation for the 'get_erc1155_tokens' tool, which defines the input schema, parses arguments, executes the GraphQL query using the client, and returns the result.
    case "get_erc1155_tokens": {
      const schema = z.object({
        owner: RoninAddress.optional(),
        tokenType: Erc1155TypeEnum,
        from: z.coerce.number().int().min(0).default(0),
        size: z.coerce.number().int().min(1).max(100).default(10),
      });
      const parsed = schema.parse(args);
      const variables: Record<string, unknown> = {
        tokenType: parsed.tokenType,
        from: parsed.from,
        size: parsed.size,
      };
      if (parsed.owner) variables.owner = parsed.owner;
      const data = await client.query<{ erc1155Tokens: unknown }>(
        queries.GET_ERC1155_TOKENS,
        variables
      );
      return jsonContent(data.erc1155Tokens);
    }
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. It mentions filtering by owner but does not disclose behavioral traits such as pagination behavior (implied by 'from' and 'size' parameters), rate limits, authentication needs, or what the response format looks like. This leaves significant gaps for a 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 and includes optional filtering. There is no wasted verbiage, and every part of the sentence contributes to understanding the tool's function.

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 complexity (4 parameters, no annotations, no output schema), the description is incomplete. It covers the basic purpose and filtering but lacks details on behavior, response format, and usage context relative to siblings. This is adequate as a minimum but has clear gaps for effective tool invocation.

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 parameters well. The description adds minimal value by mentioning the optional owner filter and token examples, but it does not provide additional semantics beyond what the schema specifies. 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 'Get' and resource 'ERC1155 tokens', with specific examples (runes, charms, accessories, etc.) that distinguish it from sibling tools like get_axie or get_land. It precisely defines the scope as in-game items, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear context for usage with the optional owner filter, but it does not explicitly state when to use this tool versus alternatives like get_axie_equipment or search_axies. It implies usage for ERC1155 tokens but lacks explicit exclusions or comparisons to sibling tools.

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