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

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_user_chat_boosts

Retrieve boosts that a user has added to a chat. Useful for tracking user contributions and chat boost status.

Instructions

Get boosts added by a user to a chat.

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_id": "<user_id>"
    },
    "name": "get_user_chat_boosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoChat ID (defaults to log group)
user_idYesUser ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the read operation but does not mention permission requirements, failure conditions, or result characteristics (e.g., pagination).

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 a single sentence with 8 words, very concise and clear. It front-loads the core purpose. However, it may be overly terse, lacking any structural benefits like bullet points.

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?

Given the absence of annotations and output schema, the description should provide more behavioral and contextual information. It is too minimal for a complete understanding, even for a read 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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the JSON schema already provides for chat_id and user_id.

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 action ('Get'), the resource ('boosts'), and the scope ('by a user to a chat'). It is specific and distinguishes this tool from sibling tools like get_chat_administrators or get_user_profile_photos, as boosts are a unique resource.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or exclusion criteria. The description offers no context for appropriate usage.

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