Skip to main content
Glama

list_indicators

Retrieve all indicator names from the echolon catalog, with an optional filter for indicators that have a period-like lookback parameter.

Instructions

Return all indicator names in the echolon catalog, optionally filtered by lookback semantics.

    Args:
        has_lookback: Optional filter.
            ``True`` → only indicators with a period-like parameter
            (e.g. RSI, ATR — sweepable single-dim lookback).
            ``False`` → only indicators without a period parameter
            (no-param indicators like OBV, multi-param scalar indicators
            like BBANDS, special-config indicators).
            Omit for all.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
has_lookbackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description provides behavioral context: the filter's effect (True/False/Omit) and examples (RSI, ATR, OBV). This is sufficient for a read-only list operation, though it omits details like sorting or pagination.

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 description is front-loaded and concise, though the docstring-style Args format adds minor verbosity. Every sentence serves a purpose, and the length is appropriate for the complexity.

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?

Given the simple input (one optional parameter) and presence of an output schema, the description covers the essential context. It explains the parameter thoroughly, leaving output details to the schema.

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

Parameters5/5

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

The description fully explains the single parameter 'has_lookback' with concrete semantics for each value (True, False, Omit) and examples. Schema coverage is 0%, so the description compensates completely.

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 clearly states it returns indicator names from the catalog with optional filtering. The verb 'return' and resource 'indicator names' are specific, but it does not explicitly differentiate from sibling tools like indicator_info or indicator_params.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. With many sibling tools (indicator_info, indicator_params, etc.), the description should indicate what distinguishes listing names from other operations.

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/DolphinQuant/echolon'

If you have feedback or need assistance with the MCP directory API, please join our Discord server