Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Alert options for a symbol

alert_options
Read-onlyIdempotent

Fetch the configuration options for setting a Stockbit alert on a symbol, including watchable categories, allowed expirations, and current values.

Instructions

What an alert on one symbol can watch, the allowed expirations and the current values.

Returns (Stockbit's data field): data{categories[{..., types[{item, lengths[{name}], ...}]}], ma_lengths[{name ('ITEM_MA_5'...)}], expirations[{expiration, ...}]}

Endpoint: GET exodus /alert/v2/initialization.

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>"
    },
    "name": "alert_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker the alert form is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description adds the endpoint and, importantly, the shape of the returned data field (categories/types/lengths, ma_lengths, expirations), which is real added context given there is no output schema, but it says nothing about caching, validity of the symbol, or auth needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and earns its place, and the endpoint line is cheap and useful. The raw Returns line is a dense unformatted field dump that costs readability, though it does carry genuine contract information.

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 read-only one-parameter lookup with no output schema, the description does supply a return-field sketch, which is the main missing piece annotations cannot cover. It still lacks the operational framing (when to call it relative to alert_create, symbol validation behavior) that would make it complete.

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 the single required parameter already carries 'Ticker the alert form is for'. The description only echoes that the alert concerns one symbol, adding no format, casing, or validity constraints beyond the schema.

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?

The description states a specific resource: the catalog of what an alert on a given symbol can watch, the allowed expirations, and current values. That is enough to separate it from mutation siblings like alert_create or listing siblings like alert_list, though it never names an alternative and the phrasing is a noun fragment rather than a verb+resource statement.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisite conditions, and no named alternative. An agent must infer from the name alone that this is the discovery call that precedes alert_create.

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