LuxAlgo MCP

My saved Vela layouts

layouts_list

Read-only

The signed-in member's saved Vela layouts (workspaces), newest first: each one's name, id, when it was last saved, whether it has a share link, and its Vela link (chart_url) that opens that layout. Use it when the member asks for their saved charts or layouts or wants one opened. Read only: it cannot save, rename, share or delete a layout. For a single market on a chart, give that market's chart_url instead. 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": {
      "context": "<context>"
    },
    "name": "layouts_list"
  }
}

Input Schema

Name	Required	Description	Default
`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."

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with an explicit negative capability list ('cannot save, rename, share or delete'), which is useful but partly redundant. Where it genuinely adds value is ordering ('newest first'), the returned fields, and the OAuth sign-in prerequisite — details no structured field supplies.

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 what the tool returns, then usage, then constraints and auth — a sensible order with no filler sentences. The field enumeration is slightly list-heavy, but each item tells the agent what it will get back, so it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description compensates by naming the return fields and their order. Combined with the auth requirement and the read-only constraint, an agent has everything needed to call this zero-configuration list tool correctly.

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?

There is a single parameter (context) with 100% schema description coverage, so the schema fully carries its semantics. The description contributes nothing about that parameter, which is acceptable at full coverage but is the baseline rather than added value.

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 ('saved Vela layouts (workspaces)') and immediately enumerates the returned fields (name, id, last-saved time, share-link flag, chart_url). An agent can distinguish this listing tool from chart_open, chart_peek, or watchlists_list without opening any schema.

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 a clear triggering condition ('when the member asks for their saved charts or layouts or wants one opened') and an exclusion pointing to a different mechanism ('for a single market on a chart, give that market's chart_url instead'). It stops short of naming the sibling tool that would be the alternative, so the routing depends on the model knowing sibling names.

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.