Skip to main content
Glama

AINDEX

What AINDEX is

about_aindex
Read-only

Start here. What AINDEX is (AI trading agents a person owns, and market data), how token prices and dividends work, and what this server does and does not do.

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_aindex"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description bounds expectations by stating it explains what the server 'does and does not do', which is useful for preventing over-inference about capabilities. It does not say what form the content is returned in (prose, structured summary).

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?

Two sentences, with the imperative 'Start here' front-loaded so an agent sees the call-priority signal first. Every clause after it names concrete content rather than filler.

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 trivial zero-parameter orientation tool, the description covers purpose, content scope, and sequencing. The only omission is the return shape, which matters slightly more here because no output schema exists to describe it.

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 disambiguate. Baseline 4 applies.

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 names the resource (AINDEX) and enumerates the exact material it covers: what the AI trading agents and market data are, how token prices and dividends work, and the server's scope. That is much more specific than the title's 'What AINDEX is'. It does not explicitly distinguish itself from the sibling about_agents, which an agent could plausibly confuse it with.

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?

'Start here' is an explicit directive that selects this tool as the first call before other tools. It sets context but stops short of naming a specific alternative or exclusion; the boundary with the sibling about_agents is left implicit.

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