Skip to main content
Glama
Sign In
Claudegram

Claudegram

by sanjar-x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pin_message

Pin a message in a Telegram chat. Optionally notify participants of the new pin or pin only for yourself in private chats.

Instructions

Закрепить сообщение в чате.

Args: notify: True — отправить уведомление участникам о новом pin. pm_oneside: только в PM — закрепить только у себя, не у собеседника.

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": {
      "chat": "<chat>",
      "message_id": "<message_id>"
    },
    "name": "pin_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
notifyNo
message_idYes
pm_onesideNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds context about the notify behavior (sends notifications) and pm_oneside (PM-only self-pin), but does not disclose other behavioral traits such as whether an existing pin is replaced.

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 extremely concise: two clear sentences. The main action is front-loaded, followed by parameter explanations. Every sentence carries useful information without redundancy.

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?

For a simple pin operation with an output schema present, the description adequately covers the core action and the non-default parameter behaviors. However, it lacks details on defaults (though schema provides them), edge cases, and the meaning of chat/message_id, making it only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains notify and pm_oneside, but omits the required parameters chat and message_id. Chat has an ambiguous type (anyOf integer/string) and message_id lacks any format context, leaving essential params poorly specified.

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 uses a specific verb 'Закрепить' (pin) and resource 'сообщение в чате' (message in chat), clearly indicating the action and its target. This distinguishes it from the sibling tool unpin_message without needing explicit contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context is implied: pinning is a well-known chat operation. However, there is no explicit guidance on when to use this tool versus alternatives like unpin_message, and no mention of exclusions or prerequisites.

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