Skip to main content
Glama
Sign In
Telegram MCP Enhanced

Telegram MCP Enhanced

by sahajp0618-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_draft

Saves a draft message for a specified Telegram entity (chat ID, username, phone number, or 'me'). Returns success or error; verify entity with search if unsure.

Instructions

Set a draft message for a specific entity.

Sets a draft message for an entity specified by username, chat_id,
phone number, or 'me'.

!IMPORTANT: If the entity is not found, it will return an error message.
If you are not sure about the entity, use the `search_dialogs`
tool and ask the user to select the correct entity from the list.

Args:
    entity (`str`):
        The identifier of the entity to save the draft message for.
        This can be a Telegram chat ID, a username, a phone number, or 'me'.

    message (`str`):
        The message to save as a draft.

Returns:
    `str`:
        A success message if saved, or an error message if failed.

Input Schema

NameRequiredDescriptionDefault
entityYes
messageYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description does disclose the failure mode (entity not found returns an error) and that results come back as strings. It does not say whether an existing draft is overwritten, whether any auth/permission is required, or that nothing is actually sent — meaningful gaps for a mutation tool with zero annotation coverage.

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?

The opening two sentences say the same thing twice ('Set a draft message for a specific entity' / 'Sets a draft message for an entity specified by...'). The Returns block duplicates the existing output schema, adding bulk without new information.

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 two-parameter write tool with an output schema present, the definition covers identifier formats, the lookup-failure path, and result shape. The overwrite behavior and send-vs-draft distinction are the remaining things an agent would want.

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 0%, so the description must carry the parameter meaning, and the Args block does: entity accepts a chat ID, username, phone number, or 'me', which the bare schema does not convey. The message parameter is only restated, so not every parameter gains extra meaning.

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 names a specific verb and resource ('Set a draft message') and scopes it to an entity. It implicitly distinguishes itself from the read-side sibling get_draft and from send_message, though it never explicitly contrasts with them.

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?

Gives a concrete when-not path: if the entity is uncertain, call `search_dialogs` and have the user pick. That is real routing guidance. It stops short of stating that this only stages a draft and does not transmit it, which is the key distinction from send_message.

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