Skip to main content
Glama
Sign In
telegram-bot-mcp

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_chat_menu_button

Fetch the current menu button for a specific private chat or the default button.

Instructions

Get the current menu button for a private chat or default.

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": "get_chat_menu_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoUser ID for private chat (optional - if omitted, returns default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as permission requirements, rate limits, or what happens with invalid chat IDs. It only states the basic read operation.

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 a single concise sentence of 11 words with no redundancy. It front-loads the essential purpose without unnecessary elaboration.

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?

While the tool is simple, the description lacks details about return values or what constitutes a 'menu button'. Without an output schema, the agent might need more context to interpret the response.

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% and the schema already describes the 'chat_id' parameter well. The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 description clearly states the verb 'Get' and the resource 'current menu button' with scope 'for a private chat or default'. It effectively distinguishes this tool from sibling 'set_chat_menu_button' which does the opposite operation.

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 description implies usage for retrieving the current menu button, but does not explicitly state when not to use or provide alternatives. However, the context of sibling tools makes the intent clear.

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