Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by dikaglorya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Add contact

telegram_add_contact

Save a Telegram user as a contact using their @username or user ID and a first name. Use it to add contacts when managing Telegram from an agent.

Instructions

Save a Telegram user as a contact by @username or user id.

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": {
      "user": "<user>",
      "firstName": "<firstName>"
    },
    "name": "telegram_add_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYes
phoneNo
lastNameNo
firstNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare this as a non-read-only, open-world operation, and the description only restates the save-contact behavior. It does not disclose permission requirements, duplicate-contact behavior, whether phone is needed, or what happens on success.

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?

A single efficient sentence with the core action and identifier forms front-loaded. There is no redundant or filler text.

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 mutation tool with four parameters and no output schema, the description is too sparse. It leaves required parameter semantics, side effects, and failure/duplicate behavior undocumented.

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% for four parameters. The description usefully clarifies that 'user' accepts an @username or user id, but it does not explain the required 'firstName' or the optional 'phone' and 'lastName' parameters.

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 gives a specific verb and resource ('Save ... as a contact') and clarifies that the user can be identified by @username or user id. It is clear against most siblings, but it does not explicitly distinguish itself from nearby contact/user tools such as get_contacts, delete_contacts, or search_users.

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?

It explains the acceptable user identifier formats but gives no guidance on when to use this tool versus alternatives like search_users, get_contacts, or send_contact. No prerequisites, duplicate-handling conditions, or exclusions are stated.

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