telegram-mcp

by draiqw

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

tg_contact_edit

Manage Telegram contacts: add by phone number, delete existing, or attach a private note visible only to you.

Instructions

Add a contact by phone number, delete one, or keep a private note on a person.

Args: phone, name, last_name: add a new contact. user: who to act on when deleting or noting. delete: remove the contact. note: private note attached to that contact. Only the owner ever sees it — it is not sent anywhere and the person cannot read it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tg_contact_edit"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`note`	No
`user`	No
`phone`	No
`delete`	No
`last_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 17, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the private nature of the note (only owner sees, not sent anywhere). However, it doesn't mention potential side effects like deletion irreversibility, overwriting existing contacts, or permission requirements, leaving notable behavioral gaps.

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 concise and front-loaded, with a one-sentence summary followed by a structured Args list. Every sentence adds value; there is no fluff or redundancy.

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

Completeness3/5

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

With six parameters and three operations, the description is mostly adequate but leaves ambiguities: 'user' is not fully explained, and there are no notes about edge cases like conflicting parameters or behavior when adding an existing contact. The presence of an output schema lessens the burden for return values, but overall the description is just minimally viable.

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 compensate. It effectively explains the role of each parameter: phone, name, last_name for adding; user for delete/note; delete flag; and note with privacy semantics. It adds meaning beyond the schema, though it lacks format details (e.g., phone format, user ID vs username) and combination constraints.

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 first sentence clearly states three specific operations: add a contact by phone number, delete one, or keep a private note. This distinctively identifies the tool's purpose and differentiates it from sibling tools like tg_contacts (listing) and generic tg_edit.

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?

The Args section explicitly defines which parameters are used for adding, deleting, or noting, providing clear operational usage context. It does not explicitly name alternatives or exclusions, but the usage patterns are unambiguous enough for an agent to select this tool among siblings.

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

Deploy Server