Skip to main content
Glama
Sign In
codex-telegram

codex-telegram

by briejhxh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

telegram_get_pinned_message

Read-only

Retrieve the currently pinned message from a known Telegram chat, including its text and metadata.

Instructions

Read the currently pinned message in a known Telegram chat. Returns text and metadata only.

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_id": "<chat_id>"
    },
    "name": "telegram_get_pinned_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes safety, and the description adds that only text and metadata are returned. However, it does not disclose behavior when no message is pinned, what happens with an invalid chat_id, or any error/edge-case behavior.

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, front-loaded sentence with no wasted words. The verb, object, and output scope are all presented immediately.

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 tool's low complexity—one required integer parameter and read-only behavior—the description covers the essential purpose, input constraint, and return scope. The absence of an output schema leaves the exact response shape unspecified, but the simple nature of the tool makes this a minor 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?

The schema only defines chat_id as an integer with 0% description coverage. The description adds the useful 'known Telegram chat' constraint, implying the ID must refer to an already resolved chat, but it does not explain the ID format or how to obtain it.

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 ('Read'), the specific resource ('currently pinned message'), and the context ('in a known Telegram chat'). It is easily distinguished from sibling tools like get_messages or search_messages because it explicitly targets the pinned message.

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?

There is no explicit guidance about when to use this tool versus alternatives, nor any mention of when-not-to-use it. The phrase 'known Telegram chat' implies a prerequisite, but no alternative tools or conditions are referenced.

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