Skip to main content
Glama
LuxAlgo

LuxAlgo Library MCP

Official
by LuxAlgo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Library indicators

library_list_indicators

Browse LuxAlgo indicators by family, concept, tags, platform, or plan tier with server-side sorting. Find structured lists like latest indicators or volatility-family tools.

Instructions

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
NameRequiredDescriptionDefault
pageNoDefault 0
sortNoDefault: date
tagsNoTag ids (from library_list_tags); an indicator must carry every tag
textNoServer-side text filter
tierNoOnly indicators included in this LuxAlgo plan tier
familyNo
conceptNoConcept slug — only indicators linked to this concept, e.g. 'rsi'
platformNoTrading platform the indicator supports, e.g. 'metatrader'
directionNo
page_sizeNoDefault 24

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / concept
      Added value: +{
+  "description": "Concept slug — only indicators linked to this concept, e.g. 'rsi'",
+  "type": "string"
+}
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • 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"
+}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden, and it does a good job: it discloses server-side sorting, default newest-first ordering, AND-combination for tags, and what a concept slug means. It does not explicitly mention pagination behavior or response shape, but the schema documents page/page_size defaults and there is no mutation or auth concern implied.

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?

Three compact sentences front-load the core behavior, list the filter dimensions, and close with concrete use cases and sibling routing. Every sentence earns its place with no repetition of schema details.

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 read-only browsing tool with 10 optional parameters, the description covers the main filter dimensions, sorting semantics, and the key sibling split. Minor gaps remain around supported platform values and return/pagination shape, but these are partly covered by the schema and not critical for correct invocation.

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?

Schema coverage is 80%, so the baseline is 3, and the description adds meaningful semantics: it explains the concept slug as 'implementations of one concept', sources tags from library_list_tags, and clarifies AND-combination. It also clarifies the default sort ordering, which informs the sort parameter.

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?

The description names a specific action and resource: 'Browse the indicator catalog with filters and server-side sorting'. It explicitly contrasts itself with library_search ('for keyword discovery prefer library_search'), so an agent can distinguish this structured-browsing tool from its closest sibling.

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?

It gives explicit when-to-use examples ('latest indicators', 'everything in the volatility family', 'indicators implementing liquidity sweeps') and states the alternative for keyword-style queries. It also tells the agent that tag ids must come from library_list_tags, connecting it to the correct sibling tool.

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

Deploy Server

Other Tools