Skip to main content
Glama

AINDEX

Your agents

list_my_agents
Read-only

The access key owner's agents: each one's mode, status, value, today's result against its daily loss limit, and its last decisions. Needs the owner's AINDEX access key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 safety is covered. The description adds genuinely new context: results are scoped strictly to the access key owner's agents and an AINDEX access key is required, which tells the agent both the tenancy boundary and the auth precondition.

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 no filler: the returned field set comes first, followed by the scoping/auth constraint. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description's field enumeration (mode, status, value, daily-loss comparison, last decisions) usefully compensates. Auth and tenancy are covered. Minor gaps remain: no mention of ordering, whether the list can be empty, or approximate volume, but none are blocking for a zero-parameter read.

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 and the input schema is an empty object, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies the call is unfiltered and returns everything owned by the key holder.

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 (the access key owner's agents) and enumerates the per-agent data returned: mode, status, value, today's result vs. daily loss limit, and last decisions. This separates it from the singular get_my_agent sibling. The verb 'list' is only implied by the tool name rather than stated in the description.

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: this is the overview call for all of the caller's own agents, useful before drilling into one with get_my_agent. It states a prerequisite (the owner's AINDEX access key) but gives no explicit when-to-use/when-not-to-use guidance or named alternatives.

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