Skip to main content
Glama
Sign In

BitCLI — Crypto Futures & Order Flow

by io.bitcli.mcp
OverviewDiscussionsAdmin

send_notification

BEHAVIOR: Outbound messaging operation. Routes proactive notifications to the human trader's verified Telegram chat, channel, or Discord webhook. Dispatches discretionary trade ideas, market condition updates, or risk reports to keep the user informed without waiting for prompts.

PRICING: $0.001 USD per dispatch. Deducted from daily tariff quota or USD balance.

PARAMETER INTERACTIONS:

  • 'target': Destination identifier string obtained from user_account.list_destinations. Prefixes determine transport: 'tg_user:' / 'tg_channel:' for Telegram, 'out_wh:' for Discord webhooks. Must belong to the authenticated account.

  • 'message': Main message body. For Telegram, supports HTML tags. For Discord, maps to the embed description.

  • 'title': Optional subject line. For Discord, renders as the embed headline. For Telegram, prepends as a bold header if provided.

RETURNS: Structured JSON confirming transmission: 'status' ('dispatched'), 'target', 'message_length', 'timestamp_utc', and '_usage' (cost_usd and remaining quota/balance).

USAGE GUIDELINES: Call user_account with action='list_destinations' prior to sending to retrieve valid target strings. Use this tool exclusively for informative messaging and human-in-the-loop updates. Do NOT use this tool to monitor market prices or set execution triggers (use alert_manager instead).

ERRORS: Unauthenticated calls, unverified/foreign destinations, empty messages, or exhausted quotas return an explicit 'isError: true' payload.

Input Schema

NameRequiredDescriptionDefault
titleNoOptional headline used as Discord embed title or Telegram bold subject line.
targetYesVerified delivery route (e.g. 'tg_user:12345678', 'out_wh:discord_vip') retrieved via `user_account.list_destinations`.
messageYesNotification content. HTML tags supported for Telegram: <b>, <i>, <code>, <pre>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / message / description
      Previous value: -"Text message body to send. Supports Telegram HTML formatting tags: <b>bold</b>, <i>italic</i>, <code>code</code>, <pre>code block</pre>."New value: +"Notification content. HTML tags supported for Telegram: <b>, <i>, <code>, <pre>."
    • changedInput schema / properties / target / description
      Previous value: -"Verified destination target obtained via `user_account.list_destinations` (e.g. 'tg_user:12345678' or 'out_wh:discord_vip')."New value: +"Verified delivery route (e.g. 'tg_user:12345678', 'out_wh:discord_vip') retrieved via `user_account.list_destinations`."
    • changedInput schema / properties / title / description
      Previous value: -"Optional brief subject header (used for Discord embed titles)."New value: +"Optional headline used as Discord embed title or Telegram bold subject line."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description must carry the full burden, and it does: per-dispatch cost ($0.001) and quota/balance deduction, authentication and destination-ownership requirements, error conditions (unverified/foreign destinations, empty messages, exhausted quotas), and the JSON return payload. These are operational traits an agent cannot infer from the schema.

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?

Labelled sections (BEHAVIOR, PRICING, PARAMETER INTERACTIONS, RETURNS, USAGE GUIDELINES, ERRORS) front-load the purpose before details. Slightly verbose in places — the RETURNS block partly duplicates what a caller would get anyway — but nearly every line carries actionable information.

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?

For a 3-parameter side-effecting messaging tool with no annotations and no output schema, the description supplies everything needed: cost model, auth preconditions, destination format, transport-specific formatting, error surfaces, and return shape. Nothing material is left implicit.

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 coverage is 100%, so the baseline is 3; the description earns above that by explaining the target prefix grammar ('tg_user:'/'tg_channel:'/'out_wh:') and how 'title' and 'message' render differently per transport (Discord embed headline/description vs. Telegram bold header/HTML body). These behavioral mappings are only partially present in 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?

States a specific verb and resource ('Outbound messaging operation ... routes proactive notifications to the human trader's verified Telegram chat, channel, or Discord webhook') and enumerates the message classes it carries. It is clearly distinguishable from alert_manager (triggers/monitoring) and user_account (destination discovery).

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?

Explicitly says to call `user_account` with action='list_destinations' before sending, restricts the tool to informative messaging and human-in-the-loop updates, and names the alternative ('Do NOT use this tool to monitor market prices or set execution triggers (use `alert_manager` instead)'). Both when-to-use and when-not-to-use are covered.

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

All BitCLI — Crypto Futures & Order Flow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources