Skip to main content
Glama
overpod

MCP Telegram

telegram-set-business-location

Set or clear the physical location (address and optional geo coordinates) for a Telegram Business account.

Instructions

Set Telegram Business physical location (address + optional geo coordinates). Requires Telegram Business subscription. Pass clear=true to remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoPass true to remove business location
addressNoStreet address text
latitudeNoGeo latitude (-90 to 90)
longitudeNoGeo longitude (-180 to 180)
Behavior4/5

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

Annotations indicate a write operation (readOnlyHint=false) and open parameters (openWorldHint=true). The description adds value by stating the Business subscription requirement and the clear=true behavior. It does not contradict annotations.

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?

Two sentences efficiently convey purpose, prerequisite, and special case. Front-loaded and no fluff.

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?

Given the parameter count (4), full schema descriptions, and no output schema, the description covers the core functionality and a key edge case (clear). Could optionally mention return value or success confirmation, but not necessary for a simple set operation.

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 coverage is 100% with parameter descriptions. The description adds meaning by summarizing 'address + optional geo coordinates' and explaining clear=true usage. This is helpful but not essential given the schema already documents each parameter.

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?

Description clearly states the action verb 'Set', the resource 'Telegram Business physical location', and the specific data (address + optional geo coordinates). It also covers the clear operation. This distinguishes it from siblings like telegram-set-business-hours or telegram-set-business-intro.

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?

Explicitly mentions prerequisite (Telegram Business subscription) and gives clear instruction for clearing location. However, it does not explicitly state when to use this tool over siblings or when not to use it, but the context makes it reasonably clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/overpod/mcp-telegram'

If you have feedback or need assistance with the MCP directory API, please join our Discord server