Skip to main content
Glama

Alerts: channels, the bot and a deep link for a coin

alert_options
Read-only

How to get funding alerts from the radar: the public Telegram channels (RU/EN, extreme events, delayed), the personal bot with instant alerts and custom conditions (free during the open beta), and a deep link that opens the bot with the coin already set. MCP is anonymous and cannot subscribe anyone — this tool only explains and links.

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_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoCoin to pre-fill in the bot deep link (BTC, ETH, 1000PEPE)
langNoLanguage of the summary and links: 'en' (default) or 'ru'

Output Schema

NameRequiredDescriptionDefault
dataYesCompact numbers the conclusion is based on, units named inside
linkYesLive page with the same data
summaryYesOne-line conclusion — quote this

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond readOnlyHint=true by disclosing the critical behavioral fact that 'MCP is anonymous and cannot subscribe anyone' — preventing an agent from promising a subscription it cannot deliver. Also surfaces that custom conditions are free during the open beta. Missing only a statement of what the response looks like, which the output schema already covers.

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?

A single sentence with parallel structure — three named options in the order the subsequent clauses address them — followed by one short scope-limiting clause. No filler and the most important constraint is placed at the end for emphasis.

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 two-optional-parameter informational tool with an output schema and readOnlyHint, nothing needed to call it correctly is absent: purpose, option taxonomy, and the key limitation are all stated.

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 coverage is 100%, so 'coin' and 'lang' are already documented in the schema. The description reinforces the coin parameter's role ('a deep link that opens the bot with the coin already set') but says nothing about the lang parameter or the fallback when coin is omitted. Baseline 3 applies since the schema carries the specification.

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?

Names the resource precisely (public Telegram channels, personal bot, deep link) and states the deliverable: 'this tool only explains and links.' An agent can immediately tell this returns alert-option guidance rather than alert data, which cleanly separates it from funding_events or funding_history.

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?

The parenthetical detail about channel types (RU/EN, extreme events, delayed) versus the bot with instant alerts and custom conditions gives an implicit map of which option a user wants. It lacks an explicit 'use this when...' sentence or a named alternative tool, but for a self-contained documentation tool the context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources