Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Alerts

alert_list
Read-onlyIdempotent

Retrieve your Stockbit alerts with optional filters for symbol or status, including alert rules and pagination metadata.

Instructions

The account's alerts, optionally for one symbol or status.

Returns (Stockbit's data field): data{alerts[{id, name, symbol, rules{and[{condition{item,operator,value}}]}, status ('STATUS_ACTIVE'|'STATUS_INACTIVE'|'STATUS_TRIGGERED'), expiry, expired_at, created_at, updated_at}]}, metadata{page, limit, total} (next page while page*limit<total)

Endpoint: GET exodus /alert/v2.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "alert_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based Default 1.
limitNoUI 30 (poller) / 50 (triggered list)
statusNostatus
symbolNoRestrict to ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds meaningful behavior beyond annotations by documenting the returned alert structure, status values, metadata pagination, and the next-page condition, though it does not mention auth requirements or rate limits.

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 description is front-loaded with the core purpose, then gives the return shape and endpoint. The return schema is long but justified because there is no output schema; the main text could be slightly more structured, but it is not padded.

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?

With no output schema available, the description sufficiently explains the return payload, status enum values, pagination metadata, and next-page rule. For a read-only filtered-list endpoint with four optional parameters, this is complete enough to invoke 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?

Schema description coverage is 100%, so the input schema already documents page, limit, status, and symbol. The description reinforces that symbol and status are optional filters and exposes status values in the return shape, but it adds little syntax or interpretation beyond the schema baseline.

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 clearly identifies the resource as the account's alerts and notes the optional symbol/status filters. It does not explicitly use a list verb or name sibling alternatives, but the read-only listing purpose is still distinguishable from alert_create, alert_delete, and alert_set_status.

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?

It implies usage by saying alerts can be filtered by symbol or status, but it does not explicitly state when to use this tool versus alert_options or other alert-related siblings. There is enough context to infer listing existing alerts, but no explicit when-to-use or exclusion guidance.

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