Skip to main content
Glama

Get a link to go live on acubic.ai

acubic_go_live
Read-onlyIdempotent

Returns a signed link, valid 15 minutes, to automate one strategy on acubic.ai with the person's own eToro or Trading 212 account, where they connect the broker and activate it. It also says whether the plan includes live portfolios. Use it whenever the person wants to automate or go live; for a running portfolio use acubic_get_portfolio.

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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "acubic_go_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
strategy_idYesThe strategy to continue on acubic.ai.

Output Schema

NameRequiredDescriptionDefault
urlNohttps://acubic.ai/go-live#t=<signed token>
errorNo
stepsNoWhat the person will meet on the website, in order.
expires_atNo
plan_checkNo
strategy_idNo
strategy_nameNo
execution_noticeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds real value by disclosing the 15-minute link validity and the fact that the end user must connect the broker and activate on acubic.ai themselves. It also notes the response indicates whether the plan includes live portfolios, which the agent needs in order to frame the next step. Missing only what happens after expiry or whether re-invocation is the recovery path.

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?

The core deliverable (signed 15-minute link) is front-loaded and nothing is padded. The sentence 'It also says whether the plan includes live portfolios' is slightly loose in its referent ('it' is ambiguous) but still carries distinct information.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description still supplies the essential hand-off detail (link lifetime, user-side broker connection step) that an agent would otherwise have to guess from the tool's complexity.

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 description coverage is 100% for both parameters, so the schema already explains strategy_id and the locale enum. The description adds no syntax, format, or scoping detail beyond that, which is the baseline case rather than a strength.

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 artifact ('Returns a signed link ... to automate one strategy'), the acting account ('the person's own eToro or Trading 212 account'), and explicitly distinguishes itself from acubic_get_portfolio. An agent can tell this apart from its sibling tools 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 Guidelines5/5

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

Gives an explicit trigger ('Use it whenever the person wants to automate or go live') and names the alternative with the condition that selects it ('for a running portfolio use acubic_get_portfolio'). Both the when and the when-not are present, with no inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources