telegram-bot-mcp

send_contact

Send a contact (phone number and first name) to a Telegram chat or default log group. Options include vCard, last name, and reply markup.

Instructions

Send a contact to a chat. If chat_id is omitted, sends to the default log group.

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": {
      "phone_number": "<phone_number>",
      "first_name": "<first_name>"
    },
    "name": "send_contact"
  }
}

Input Schema

Name	Required	Description
`vcard`	No	vCard data
`chat_id`	No	Chat ID or @channel_username. Optional — defaults to log group
`last_name`	No	Contact last name
`first_name`	Yes	Contact first name
`phone_number`	Yes	Phone number
`reply_markup`	No	JSON string with reply markup
`protect_content`	No	Protect message from forwarding/saving
`reply_parameters`	No	JSON object with ReplyParameters (e.g. {"message_id": 123})
`message_thread_id`	No	Topic/thread ID for supergroups with topics enabled
`disable_notification`	No	Send silently without notification

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.3Mar 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral disclosure burden. It mentions the default log group behavior but does not disclose side effects (e.g., whether a chat is created, error handling), permissions, or rate limits. The 'send' verb implies message creation, which is consistent.

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?

The description is concise (two sentences) and front-loads the primary action. No unnecessary words, but the omission of usage guidelines reduces efficiency.

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?

Given 10 parameters with many optional ones (e.g., reply_markup, protect_content), the description is too minimal to cover interactions or best practices. No output schema means description should clarify return value, but it doesn't. Adequate for basic understanding but incomplete for comprehensive use.

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 100%, so the description adds limited value beyond the schema. The only additional semantic is the default chat_id behavior. The description does not enhance understanding of parameter relationships or usage patterns.

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 clearly states the action ('Send a contact') and resource, with a concise note about default behavior when chat_id is omitted. It distinguishes from other send_* siblings by focusing on contact-specific action, though not explicitly differentiating.

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?

The description only provides guidance on the optional chat_id default. It lacks any indication of when to use this tool versus other send tools (e.g., send_message for text), no exclusions, and no alternatives mentioned.

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

Deploy Server