Skip to main content
Glama

mcp-server

by io.github.tickerbot

tickerbot_subscribe_ticker

Register a webhook that fires when one ticker matches a condition. condition is a SQL WHERE-clause fragment scoped to that ticker (e.g. "rsi_14 > 70 AND relative_volume > 2"). Pass target_url for an https POST, or channel:"discord" + discord_url to post to Discord; omit for in-app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoHuman-readable label.
tickerYesSymbol.
cadenceNoEvaluation cadence. Default realtime; hourly/nyse_open throttle. (`1m` accepted as a deprecated alias of realtime.)
channelNoDelivery channel: `webhook` (POST to target_url), `discord` (embed to discord_url), `mobile_push` (to a registered device), or `in_app` (dashboard only). Inferred from the URL you pass if omitted.
conditionYesSQL WHERE fragment evaluated for this ticker.
device_idNoRegistered device id from the mobile app. Required when channel is "mobile_push".
target_urlNoOptional https URL for the `webhook` channel; omit for in-app.
discord_urlNoDiscord incoming-webhook URL (https://discord.com/api/webhooks/…). Required when channel is "discord".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cadence / description
      Previous value: -"Evaluation cadence."New value: +"Evaluation cadence. Default realtime; hourly/nyse_open throttle. (`1m` accepted as a deprecated alias of realtime.)"
    • changedInput schema / properties / cadence / enum
      Previous value: -[
-  "1m",
-  "hourly",
-  "nyse_open"
-]New value: +[
+  "realtime",
+  "hourly",
+  "nyse_open"
+]
    • changedInput schema / properties / channel / description
      Previous value: -"Delivery channel: `webhook` (POST to target_url), `discord` (embed to discord_url), or `in_app` (dashboard only). Inferred from the URL you pass if omitted."New value: +"Delivery channel: `webhook` (POST to target_url), `discord` (embed to discord_url), `mobile_push` (to a registered device), or `in_app` (dashboard only). Inferred from the URL you pass if omitted."
    • changedInput schema / properties / channel / enum
      Previous value: -[
-  "webhook",
-  "discord",
-  "in_app"
-]New value: +[
+  "webhook",
+  "discord",
+  "in_app",
+  "mobile_push"
+]
    • addedInput schema / properties / device_id
      Added value: +{
+  "description": "Registered device id from the mobile app. Required when channel is \"mobile_push\".",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / cadence / enum
      Previous value: -[
-  "1m",
-  "5m",
-  "15m",
-  "hourly",
-  "nyse_open"
-]New value: +[
+  "1m",
+  "hourly",
+  "nyse_open"
+]
  3. Changed3 schema fields changed
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "Delivery channel: `webhook` (POST to target_url), `discord` (embed to discord_url), or `in_app` (dashboard only). Inferred from the URL you pass if omitted.",
+  "enum": [
+    "webhook",
+    "discord",
+    "in_app"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / discord_url
      Added value: +{
+  "description": "Discord incoming-webhook URL (https://discord.com/api/webhooks/…). Required when channel is \"discord\".",
+  "type": "string"
+}
    • changedInput schema / properties / target_url / description
      Previous value: -"Optional https URL for delivery; omit for in-app."New value: +"Optional https URL for the `webhook` channel; omit for in-app."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the trigger behavior (fires on condition match), delivery methods (POST/Discord/in-app), and gives a realistic condition example. It doesn't cover edge cases like validation or idempotency, but the core behavior is well described.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose, followed by practical usage details and an example. Every sentence earns its place without redundancy.

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?

Despite 8 parameters and no output schema, the description provides enough context to select and invoke the tool correctly. It highlights the most complex parameter (condition) and the channel configuration interplay. Return values are not specified but can be inferred for a subscription creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 8 parameters with descriptions, so baseline is 3. The description adds value by explaining relationships between channel, target_url, discord_url, and provides an example of the `condition` parameter, going beyond the schema.

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?

Clearly states it registers a webhook for one ticker that fires when a condition matches, with a concrete SQL clause example. This distinguishes it from broader sibling tools like subscribe_scan or subscribe_events.

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?

Provides explicit guidance for delivery channels (target_url for HTTPS POST, discord_url for Discord, omit for in-app) and clarifies the condition format. It doesn't explicitly name alternative tools or exclusions, but the single-ticker scope is clear.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target distinct resource-action pairs, but get_ticker and get_ticker_history overlap (both return a single historical row via asof), and the four subscribe_* tools are thin wrappers around create_webhook, creating some ambiguity. Detailed descriptions mitigate but don't eliminate confusion.

Naming Consistency4/5

The tickerbot_ prefix and verb_noun pattern are consistent (create_*, get_*, list_*, delete_*, update_*), but subscribe_* deviates from create_* for webhooks, and scan/search_news are bare verbs. Overall predictable.

Tool Count2/5

35 tools is excessive for the domain; many could be consolidated (e.g., four subscribe_* variants into a single parameterized webhook creator, get_ticker/get_ticker_history into one). The breadth of data types justifies some volume, but this exceeds the 25-tool threshold for coherence.

Completeness5/5

Full lifecycle coverage for universes, custom signals, and webhooks; extensive read-side for tickers, series, bars, events, news, and scans. No critical dead ends: anything creatable can be updated/deleted/tested, and data lookups have appropriate query tools.

Resources