Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testTelegramConnection

Idempotent

Tests a Telegram bot connection by sending a message with the provided bot token, chat ID, and message thread ID to verify notification delivery.

Instructions

POST /notification.testTelegramConnection

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": {
      "botToken": "<botToken>",
      "chatId": "<chatId>",
      "messageThreadId": "<messageThreadId>"
    },
    "name": "notification-testTelegramConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdYes
botTokenYes
messageThreadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations declare openWorldHint=true and idempotentHint=true, implying an outbound network test call, but the description adds nothing beyond the path. It doesn't say what a successful test looks like, whether it sends an actual message to the chat, what errors indicate bad credentials, or any rate-limit concerns.

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

Conciseness3/5

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

Extremely short and not padded, but that's because it contains almost no information. It's a bare endpoint reference rather than a structured description with purpose and constraints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A three-parameter test tool with zero parameter documentation, no output schema, and only sparse annotations. The description doesn't close any of those gaps, leaving the agent without enough information to invoke it confidently.

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

Parameters1/5

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

Schema description coverage is 0% for all three required parameters (botToken, chatId, messageThreadId), and the description provides no explanation of their format or source. The agent must guess whether chatId is a numeric ID or a username, and what messageThreadId refers to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is just the HTTP verb and path, 'POST /notification.testTelegramConnection', which restates the name rather than stating what the tool does in plain terms. An agent must infer from the name that it tests a Telegram notification configuration using a bot token, chat ID, and thread ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance, and no mention of alternatives such as notification-testCustomConnection or notification-createTelegram. The only signal is the name itself.

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