Lemma Telepath

Reply in the bot's own DM

telegram_bot_dm_reply

Destructive

Reply to someone in the bot's OWN direct chat — the messages from telegram_bot_direct_messages — sent as the bot. This is a different conversation from that person's business chat with you, even though the chat_id is the same, so it is a separate tool on purpose: use this for the bot's DM line, and telegram_send_message for your business chats. The other person sees it and is notified, so confirm the message with the user first.

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": "telegram_bot_dm_reply"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The reply, sent as the bot.
`chat_id`	Yes	chat_id from telegram_bot_direct_messages.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the recipient sees and is notified, so confirmation is required, and that the chat_id overlaps with a different conversation. It stops short of rate limits or delivery failure behavior, so not a 5.

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

Conciseness4/5

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

Front-loaded with the core action and scope, and each sentence carries weight (the chat_id trap, the sibling routing, the confirmation requirement). Slightly dense but no wasted filler.

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-parameter messaging tool with no output schema and full annotation coverage, everything an agent needs is present: what it does, which sibling to prefer, the chat_id ambiguity, and the user-confirmation requirement.

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%, so the baseline is 3, but the description adds meaning by clarifying that chat_id comes from telegram_bot_direct_messages and that the same chat_id denotes a different conversation than the business chat — resolving a real ambiguity the schema cannot.

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 states a specific verb (Reply) and resource (the bot's OWN direct chat / bot DM line), and explicitly distinguishes it from telegram_send_message and the business chat. An agent can identify the tool without opening any schema.

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

Usage Guidelines5/5

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

It gives explicit routing: 'use this for the bot's DM line, and telegram_send_message for your business chats,' and adds a precondition ('confirm the message with the user first'). Both the when and the alternative are named.

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

All Lemma Telepath tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?