TgPilot

send_message

Send Markdown text messages to Telegram chats, with optional reply targeting and scheduled delivery.

Instructions

Send a text message (Markdown). Optional reply and scheduled send.

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

Input Schema

Name	Required	Description	Default
`chat`	Yes
`text`	Yes
`reply_to`	No
`schedule_minutes`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits beyond the schema: the body is interpreted as Markdown, and sending can be deferred ('scheduled send'). It says nothing about permissions, whether the message is irreversible once sent, message length limits, or rate limiting, which are important for an unannotated mutation tool.

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 short sentences, zero filler, and the core action is front-loaded before the optional behaviors. Nothing repeats the schema verbatim or wastes space.

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?

For a 4-parameter mutation tool with no annotations and 0% schema description coverage, the description is too thin. The existence of an output schema removes the need to explain return values, but the identifier semantics, scheduling behavior, and send-side preconditions remain undocumented.

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 description coverage is 0%, with only bare titles like 'Chat' and 'Schedule Minutes'. The description adds meaning for text (Markdown formatting), reply, and scheduling, but leaves key ambiguities: is 'chat' an ID or a name, what unit/zero-value does schedule_minutes carry, and is reply_to a message ID? It partially compensates but not fully.

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?

States a specific verb and resource ('Send a text message'), which cleanly separates it from siblings like send_file, send_poll, and forward_messages. It stops short of explicitly naming those alternatives, but the resource type is distinctive enough for an agent to route correctly.

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?

There is no when-to-use guidance: nothing says when to prefer this over send_file/send_poll, whether the chat must already be joined, or what happens if the chat is invalid. 'Optional reply and scheduled send' describes parameters, not usage conditions, so the agent must infer everything from the name.

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