Skip to main content
Glama

AINDEX

What an AINDEX agent is, its rules and its costs

about_agents
Read-only

Personal trading agents on AINDEX: what one is, the rules it can never break, and what it costs (AI credits, with prices per check for common models; AINDEX's trade fee and Lighter's own fee; a flat charge per signed transaction; no deposit or withdrawal fee). Also how a person uses their own agents from this server. No key needed.

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": "about_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a read-only, non-open-world operation. The description adds one genuine behavioral fact beyond them, 'No key needed', which tells the agent it can invoke this without authentication. It does not state that the call is free or what the response looks like, so the added value is modest.

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?

Two sentences, front-loaded with the subject and then the cost breakdown in a compact parenthetical list. The fee enumeration is dense but each item is a distinct fact an agent would otherwise have to discover elsewhere.

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 what content to expect, including the specific cost categories (AI credits, AINDEX fee, Lighter fee, per-signature charge, no deposit/withdrawal fee) and the authentication requirement. Nothing essential to invoking it is missing.

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, which is the baseline-4 case. Nothing in the description needs to explain inputs, and none is claimed.

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 uses a specific resource ('Personal trading agents on AINDEX') and enumerates the exact topics covered: what an agent is, its immutable rules, and its costs. That distinguishes it from the sibling about_aindex by subject matter, though it never explicitly says so.

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?

Usage is implied rather than stated: an agent is expected to consult this before working with the agent tools, and the closing clause notes it also explains how a person uses their own agents from this server. There is no explicit 'call this when' or 'do not call this for X' instruction pointing at siblings like about_aindex or get_agent_fees.

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