LuxAlgo MCP

List Library indicators

library_list_indicators

Read-only

Browse the indicator catalog with filters and server-side sorting (newest first by default). The Library is organized by family and concept: filter by family (keys from library_list_families) or by concept slug (that concept's implementations; slugs from library_list_concepts or library_search), and optionally by 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

Name	Required	Description
`page`	No	Default 0
`sort`	No	Default: date
`text`	No	Server-side text filter
`tier`	No	Only indicators included in this LuxAlgo plan tier
`family`	No	Family key from library_list_families, e.g. 'volatility'
`concept`	No	Concept slug (from library_list_concepts or library_search) — 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 changedOct 25, 2026

changedInput schema / properties / concept / description

Previous value: -"Concept slug — only indicators linked to this concept, e.g. 'rsi'"New value: +"Concept slug (from library_list_concepts or library_search) — only indicators linked to this concept, e.g. 'rsi'"

addedInput schema / properties / family / description

Added value: +"Family key from library_list_families, e.g. 'volatility'"

removedInput schema / properties / tags

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

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

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds real behavioral detail beyond that — default sort is newest-first, sorting is server-side, and filters compose over family/concept/platform/tier — though it doesn't describe pagination rollout or result shape.

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?

Front-loaded with the core action and default ordering, then use cases, then the alternative. Dense but every clause carries information; the trailing 'for keyword discovery prefer library_search' is well-placed. Minor length density keeps it below a 5.

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?

A 10-parameter list tool with no output schema is well served here: filtering axes, sorting default, and sibling dependencies are all covered. The only gap is that it never characterizes the returned page (fields, pagination totals) or result-shape expectations, which matters somewhat without an output schema.

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?

With 90% schema coverage the schema already documents most parameters, so the baseline is 3. The description adds genuine provenance semantics the schema cannot: family keys come from library_list_families, concept slugs from library_list_concepts/library_search, and concept filtering means 'that concept's implementations'. Page, page_size, direction, and text remain unaddressed by prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — browsing the indicator catalog with filters and server-side sorting — and immediately contrasts itself with library_search for keyword discovery. An agent can distinguish it from library_list_concepts, library_list_families, and library_search purely from 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 Guidelines5/5

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

Names explicit when-to-use scenarios ('latest indicators', 'everything in the volatility family', 'indicators implementing liquidity sweeps') and an explicit when-not with the alternative to pick instead (library_search for keyword discovery). The dependency keys are routed to the correct sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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