Skip to main content
Glama

Guardian info

guardian_info

Guardians (Aura NFTs) on X1: price, tiers and today's availability. A Guardian is bought by BURNING APEX (Ember: 2,000 APEX; higher tiers cost more) and gives a claim multiplier and a daily APEX reward. Free to call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "guardian_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description usefully discloses that the call is free, that values are for "today," and that Guardians are acquired by burning APEX. It does not explicitly state read-only behavior or describe the response shape, but it adds meaningful behavioral context beyond the bare name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and the remaining sentences efficiently add cost and acquisition context. The second sentence is background rather than invocation guidance, but it is short and relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter informational tool with no output schema, the description covers the returned fields (price, tiers, availability) and the cost profile (free). It is complete enough to call correctly, though it could explicitly name the sibling alternatives for checking versus buying.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the baseline. No parameter-level gaps exist.

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 states a specific resource (Guardians/Aura NFTs on X1) and exactly what information it returns: price, tiers, and today's availability. This clearly distinguishes it from sibling action tools such as guardian_buy and guardian_burn_build.

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?

It notes that the call is free, which is useful usage context, but it never explicitly says when to use this tool versus guardian_buy or guardian_burn_build. The intended workflow—checking info before buying or burning—is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources