Skip to main content
Glama
Johnhyeon

TelegramLens

by Johnhyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

telegram_watchlist

Track how your watchlist stocks are discussed on Telegram. Enter a stock to retrieve original mentions, channels, and links, then summarize the sentiment and issues driving the conversation.

Instructions

'내 종목/보유 종목'이 텔레그램에서 어떻게 거론되는지 — 언급 원문·요약 근거를 반환합니다.

'내 종목 분석/소식/여론/뭐래/텔레그램에서 어때' 류 요청에 호출하세요. 종가·차트·이동평균· 기술지표가 아니라 텔레그램에서 그 종목을 두고 무슨 말이 도는지(원문·채널·링크)를 줍니다. 이 데이터로 종목별 '여론·이슈'를 요약하세요(기술지표는 사용자가 원할 때만 StockLens 로). 종목 등록/삭제는 텔레그램 '!보유 설정 …' 명령으로.

Args: hours: 집계 시간 범위(시간). 기본 24.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hoursNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • removedInput schema / properties / hours / default
      Removed value: -24
  2. First observedv0.4.3

TDQS

A4.3/5.0
Behavior4/5

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

The description explains what data is returned (mentions, original text, channels, links) and its purpose in summarizing sentiment, but does not detail performance limits or data freshness. Annotations already indicate it's not destructive and is open-world, but the description adds relevant context.

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?

The description is appropriately concise, with the core purpose front-loaded. The additional notes on usage and alternatives are valuable, but slightly verbose in the middle section.

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?

For a tool with one optional parameter and a rich context of siblings, the description covers the main usage and output expectations, making it sufficiently complete for effective selection and invocation.

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 covers 0% for the single parameter 'hours', but the description provides basic semantics by stating it is the aggregation time range in hours with a default of 24. This is sufficient, though minimal.

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 tool returns mentions of the user's stocks on Telegram, including original text and summary rationale. It distinguishes itself from technical indicators and other analytical tools.

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

Usage Guidelines5/5

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

It explicitly specifies when to call (requests about Telegram mentions, sentiment, etc.) and when not to (technical indicators, charts, moving averages). It also names alternatives like StockLens for technical analysis and mentions the command for registration/deletion.

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