Skip to main content
Glama
Sign In

LuxAlgo MCP

by io.github.LuxAlgo
OverviewDiscussionsAdmin

Create a watchlist

watchlists_create

Creates a new watchlist in the signed-in member's account, optionally with its first symbols; it shows up in Vela on the web and in the Vela apps. Use watchlists_add_symbols to add to a list that exists. How many watchlists and symbols per list the member may have comes from their LuxAlgo plan: at a limit the call answers with the limit and where to upgrade, and nothing is saved. It changes the member's account, so the chat app may ask the user to confirm first. Requires signing in with a LuxAlgo account (OAuth).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "context": "<context>"
    },
    "name": "watchlists_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
etfNoFile the US listings among `symbols` under ETFs instead of Stocks.
nameYesThe list's name, e.g. "Crypto majors".
contextYesExplain 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."
symbolsNoMarkets, each a market as source:TICKER, e.g. "binance:BTCUSDT", "hyperliquid:BTC", "coinbase:BTC-USD", "edgx:AAPL" (US stocks and ETFs; "NASDAQ:AAPL" works too), "fx:EURUSD", "commodities:XAUUSD", "cme:ES1!". A bare stablecoin pair ("BTCUSDT") is read as Binance and a bare "ES1!" as CME.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true). It discloses that the watchlist propagates to Vela web and apps, that plan-limit failures return the limit plus upgrade location and save nothing, and that the chat app may request user confirmation before the write. That is exactly the kind of mutation-side context annotations cannot express.

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?

Five sentences, front-loaded with the core verb and resource, then routing, then failure behavior, then prerequisites. Every sentence carries operational information, though "it shows up in Vela on the web and in the Vela apps" is the weakest and could be trimmed to a clause.

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?

With no output schema the description must carry return behavior, and it covers the failure path precisely (limit value plus upgrade destination, nothing saved) but says nothing about what a successful response contains, such as the new list's identifier. Otherwise it is complete for a 4-parameter mutation, including auth and confirmation behavior.

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

Parameters3/5

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

Schema coverage is 100%, so name, symbols, etf, and context are already documented, including market syntax examples and the 1-50 array bounds. The description adds only the framing that symbols are the list's "first symbols," which clarifies create-with-population semantics but adds no new field-level detail. Baseline 3 is appropriate.

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 ("Creates a new watchlist in the signed-in member's account") and scopes it further with "optionally with its first symbols." It explicitly distinguishes itself from the nearest sibling by directing to watchlists_add_symbols for existing lists.

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

Usage Guidelines4/5

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

Gives clear context: use this to create; use watchlists_add_symbols to append to an existing list. It also discloses the pre-condition that the member must be signed in via OAuth and that plan limits can block creation. It stops short of naming watchlists_list as the check-before-create alternative, but the routing guidance is otherwise unambiguous.

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

All LuxAlgo MCP toolsInspect
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.

Resources