LuxAlgo MCP

List Library indicators

library_list_indicators

Read-only

Browse the indicator catalog with filters and server-side sorting (newest first by default). Filter by family, concept slug (implementations of one concept), tags (ids from library_list_tags, AND-combined), trading platform, or plan tier. Use for structured browsing — 'latest indicators', 'everything in the volatility family', 'indicators implementing liquidity sweeps'; for keyword discovery prefer library_search.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Default 0
`sort`	No	Default: date
`tags`	No	Tag ids (from library_list_tags); an indicator must carry every tag
`text`	No	Server-side text filter
`tier`	No	Only indicators included in this LuxAlgo plan tier
`family`	No
`concept`	No	Concept slug — only indicators linked to this concept, e.g. 'rsi'
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`platform`	No	Trading platform the indicator supports, e.g. 'metatrader'
`direction`	No
`page_size`	No	Default 24

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 8, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / context / description

Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""

addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedAug 31, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

Changed4 schema fields changedAug 26, 2026

addedInput schema / properties / concept

Added value: +{
+  "description": "Concept slug — only indicators linked to this concept, e.g. 'rsi'",
+  "type": "string"
+}

addedInput schema / properties / platform

Added value: +{
+  "description": "Trading platform the indicator supports, e.g. 'metatrader'",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Tag ids (from library_list_tags); an indicator must carry every tag",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / tier

Added value: +{
+  "description": "Only indicators included in this LuxAlgo plan tier",
+  "enum": [
+    "essential",
+    "premium",
+    "ultimate",
+    "ultra"
+  ],
+  "type": "string"
+}

First observedAug 12, 2026

TDQS

Score is being calculated.

All LuxAlgo MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List Library indicators

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources