Corvus

send_telegram_alert

Send formatted Telegram alerts with severity levels (info, warning, critical). Notify users about DeFi events or wallet analytics in a specified chat.

Instructions

Send a formatted message to a Telegram chat. Use this when the user explicitly asks to send information to Telegram, get an alert, or be notified. Requires the user's Telegram chat ID.

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": {
      "chat_id": "<chat_id>",
      "message": "<message>"
    },
    "name": "send_telegram_alert"
  }
}

Input Schema

Name	Required	Description
`chat_id`	Yes	Telegram chat ID (numeric ID or @username)
`message`	Yes	Message content (supports Markdown formatting)
`severity`	No	Message severity level - affects emoji prefix (default: info)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description must cover behavior. It mentions Markdown support and severity emoji prefix, but omits details like whether the call is synchronous, rate limits, or if the action is idempotent. It adequately indicates this is a write operation but lacks depth.

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 the core purpose, no filler. Every sentence adds distinct value: action, usage guidance, prerequisite.

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?

For a simple 3-param tool with no output schema, the description covers purpose, usage, parameter details, and basic behavior. Missing return value or error info, but that is acceptable given the tool's simplicity.

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%, but the description adds valuable context: chat_id format ('numeric ID or @username') and severity's effect ('affects emoji prefix'). This provides meaning beyond the schema's enum descriptions.

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?

The description clearly states the action ('Send a formatted message to a Telegram chat') and the resource ('Telegram'). It distinguishes itself from siblings, which are all data retrieval tools, by being a write/notification tool.

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 description explicitly tells when to use the tool ('when the user explicitly asks to send... get an alert, or be notified') and includes a prerequisite ('Requires the user's Telegram chat ID'). It does not list alternatives, but the sibling context makes the usage scope clear.

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

Deploy Server