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

telegram-notes-mcp

by RaspizDIYs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_chat_context

Retrieve the chat context around a specific message by providing the chat name and message ID, with an adjustable window of surrounding messages.

Instructions

Return messages surrounding a specific message in 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": {
      "chat_name": "<chat_name>",
      "around_message_id": "<around_message_id>"
    },
    "name": "get_chat_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNo
chat_nameYes
around_message_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided; description does not disclose any behavioral traits such as message ordering, size limits, or whether it returns only immediate neighbors. The agent is left to guess behavior.

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?

Single, clear sentence that efficiently conveys the purpose. Could be longer to add missing details, but no wasted words.

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 tool has 3 parameters and an output schema, the description provides insufficient context. The meaning of 'window' and the structure of returned messages are absent, leaving the agent underinformed.

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%. Description mentions chat_name and around_message_id implicitly but does not explain them. Parameter 'window' is not described at all. Output schema exists but is not referenced.

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?

Description clearly states the verb 'Return' and the resource 'messages surrounding a specific message in a chat'. Differentiates from siblings like search_messages which finds messages by query, not context.

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?

Implies usage when needing context around a message, but no explicit when-not or alternative tools are mentioned. Sibling tools like search_messages could serve similar purposes, but no guidance on selection.

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