aiogram-mcp

Overview Schema Source Related Servers Discussions Admin

send_message

Deliver a Telegram text message to any chat or user, configurable with parse mode, notification control, and reply threading.

Instructions

Send a text message to a Telegram chat or user.

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>",
      "text": "<text>"
    },
    "name": "send_message"
  }
}

Input Schema

Name	Required	Default
`chat_id`	Yes
`text`	Yes
`parse_mode`	No	HTML
`disable_notification`	No
`reply_to_message_id`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`message_id`	No
`chat_id`	No
`date`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.1Mar 16, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are present. The description does not disclose any behavioral traits such as character limits, rate limits, or whether the operation is idempotent. It fails to mention that the tool returns a message object (output schema exists).

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?

The description is a single front-loaded sentence with no superfluous information. It is appropriately concise for a simple tool.

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

Completeness2/5

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

Given 5 parameters with 0% schema coverage, multiple sibling tools, and an output schema, the description provides insufficient context. Agents lack information on parameter details, return format, and selection among similar tools.

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

Parameters2/5

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

Schema description coverage is 0%, requiring the description to compensate. It only states 'Send a text message' and does not explain the purpose or constraints of parameters like chat_id, parse_mode, or disable_notification.

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

Purpose4/5

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

The description clearly states the action (send) and the resource (text message to a Telegram chat or user). It distinguishes from siblings that send other media types like photos or animations.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like send_photo or forward_message. The description implies usage for text messages but offers no exclusions or context.

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