Skip to main content
Glama
overpod

MCP Telegram

telegram-set-business-hours

Set Telegram Business hours by defining a weekly schedule with time ranges, timezone, and optional open/closed override or clear.

Instructions

Set Telegram Business work hours — days and time ranges when your business is open. Requires Telegram Business subscription. Pass clear=true to disable the work hours display entirely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoPass true to remove business hours entirely
openNowNoManually override current open/closed status. Omit to derive from schedule.
scheduleNoWeekly schedule. Multiple ranges per day are allowed.
timezoneNoIANA timezone ID (e.g. 'Europe/Moscow', 'America/New_York'). Required when setting schedule.
Behavior4/5

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

Adds value beyond annotations by mentioning subscription requirement and the clear feature. Annotations indicate mutability and open-world, which aligns. No contradictions. Could expand on side effects like overwriting previous hours.

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?

Extremely concise with two sentences covering purpose, prerequisite, and special case. No unnecessary words.

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?

Covers core purpose, prerequisite, and a special feature. No output schema, but for a setter tool the description is sufficient. Could mention that it overwrites existing hours, but not a critical gap.

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%, so baseline is 3. Description adds only the 'clear' parameter special behavior, which provides marginal extra meaning. Other parameters are adequately defined in schema.

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?

Explicitly states the verb 'Set' and the resource 'Telegram Business work hours' with specifics on days and time ranges. Distinguishes from sibling tools like telegram-set-business-away or telegram-set-business-greeting by focusing on hours.

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?

Provides clear prerequisite ('Requires Telegram Business subscription') and a special usage case ('Pass clear=true to disable'). Does not explicitly compare to alternatives, but the sibling context makes the distinction 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