Skip to main content
Glama
Sign In
loreroom

loreroom

by fenghaochang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_recent_context

Retrieve recent Telegram conversation history to provide context when missing or when the user refers to earlier messages. Includes timestamps, sender, and content for both parties.

Instructions

撈回最近 N 小時的 Telegram 對話（含時間、發出方、內容；雙向都有）。當你缺乏上下文、或使用者提到『剛剛/今天/昨天/最近』時，務必優先呼叫本工具還原脈絡。

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": {
      "hours": "<hours>"
    },
    "name": "get_recent_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYes往回幾小時
chat_idNo限定某對話

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided. Description discloses what is returned (time, sender, content, both directions) but not limits, pagination, or side effects. Adequate for a read tool but incomplete.

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?

Two sentences: one defines function, one gives usage guidance. Zero waste, front-loaded with purpose.

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?

No output schema; description partially explains return format (time, sender, content) but lacks structure details or limits. For a retrieval tool, more completeness would be beneficial.

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 descriptions already cover both parameters (hours, chat_id) with 100% coverage. Description adds context on when to use them but no additional syntax or meaning beyond schema.

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 states the verb (retrieve), resource (Telegram conversations), and scope (last N hours, bidirectional). It distinguishes from sibling by implying this tool is for broad context retrieval when lacking context.

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?

Explicitly says when to use: 'when you lack context, or the user mentions just now/today/yesterday/recently'. Does not explicitly state when not to use, but presence of sibling suggests alternative for specific searches.

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