Skip to main content
Glama
Sign In
telegram-business-bridge

telegram-business-bridge

by AndyShaman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_context

Retrieve surrounding messages to understand the conversation thread. Use this after finding a message to get its context.

Instructions

Контекст вокруг сообщения: N соседних сообщений до и после (radius, по умолч. 5). Используй после search_messages, чтобы понять нить разговора.

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>",
      "message_id": "<message_id>"
    },
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
radiusNo
chat_idYes
message_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the default radius and the nature of the operation (reading context around a message). It does not mention error handling, permissions, or rate limits, but for a simple retrieval tool, the transparency is adequate.

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 minimal and front-loaded with the core functionality. Every sentence adds value with no redundancy. Two sentences efficiently convey purpose and usage.

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 (3 parameters, no enums or nested objects) and the presence of an output schema, the description is fairly complete. It provides usage context (after search_messages) but lacks details on edge cases like invalid message_id.

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?

The input schema has 0% description coverage, so the description must compensate. It adds meaning to 'radius' (number of neighbors, default 5), but does not clarify 'chat_id' or 'message_id' beyond their names. This is insufficient for complete understanding of the parameters.

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 it retrieves context around a message (neighboring messages) with a configurable radius. It uses specific verbs and resource, and distinguishes from siblings by recommending usage after search_messages.

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 explicitly advises using this tool after search_messages to understand conversation threads, providing clear context for when to use it. However, it does not explicitly state when not to use or provide alternatives.

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