Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Create a price alert

alert_create

Creates a Stockbit alert for one IDX symbol, triggering when price, volume, RSI, moving average, or best bid/offer crosses a threshold you set.

Instructions

Creates a Stockbit alert on one symbol: price, change, value, volume, frequency, best bid/offer, RSI(14) or price vs a moving average, compared with a threshold. alert_options lists what the account allows.

Endpoint: POST exodus /alert/v2/create.

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": {
      "symbol": "<symbol>",
      "item": "<item>",
      "operator": "<operator>"
    },
    "name": "alert_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesWhat to watch. ITEM_MA_* compares the price with that moving average.
noteNoA note shown with the alert.
valueNoThreshold (IDR for prices, percent for change). Leave out for ITEM_MA_*.
expiryNoHow long the alert lives; default one month.
symbolYesIDX ticker such as BBCA or TLKM (no exchange prefix).
operatorYesComparison; CROSSING_* fire when the item crosses the value (or the MA).
expiry_dateNoEnd date, only with EXPIRATION_CUSTOM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so duplication/severity is covered structurally. The description adds the concrete endpoint (POST /alert/v2/create) and the single-symbol-per-call scope, but says nothing about behavior on duplicate alerts, per-account alert limits, or error conditions beyond referring to alert_options.

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 capability statement is front-loaded in the first sentence, with the endpoint line as a compact footer. It is efficient, though the endpoint string contributes little to an agent's decision and the long enumeration of item types duplicates the enum.

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

Completeness3/5

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

For a 7-parameter mutation tool with no output schema, the definition covers what is created and points at alert_options for allowed item types. It stops short of stating what the call returns (e.g. an alert id) or how success/failure surfaces, which an agent would want for a create operation.

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% and already documents every parameter, including the ITEM_MA_* caveat and expiry_date pairing, so the baseline is 3. The description's mention of RSI(14) and moving-average comparisons merely restates enum contents rather than adding cross-parameter rules (e.g. what value means for each item type).

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

Purpose4/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 Stockbit alert on one symbol") and enumerates the watchable items, so an agent knows exactly what capability this exposes. It also distinguishes itself from the account-capability sibling alert_options, though it doesn't contrast with other alert siblings such as alert_set_status or alert_list.

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

Usage Guidelines3/5

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

The pointer that "alert_options lists what the account allows" implies a check-before-create step, which is useful guidance. However, there is no explicit when-to-use/when-not framing, no note on whether the symbol must already be in a watchlist, and no mention of what to do on failure.

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