TelegramLens

Overview Schema Source Related Servers Discussions Admin

telegram_velocity

Read-onlyIdempotent

Track stock mention velocity in Telegram channels by time bucket, comparing recent volume against prior baselines to detect spikes and momentum shifts.

Instructions

종목별 언급의 시간대별 흐름과 급등(velocity)을 반환합니다.

시간 버킷별 독립 언급을 집계해 직전 대비 증가율과 spike 여부를 봅니다. 베이스라인 배율(baseline_ratio) 동봉.

Args: query: 종목명/6자리 코드(생략 시 velocity 상위 top 종목). bucket_minutes: 시간 버킷 크기(분). 기본 30. window_hours: 집계 윈도우(시간). 기본 6. spike_min: 최근 버킷 급등 임계값(건수). 기본 5. top: query 미지정 시 상위 N개. 기본 15.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`top`	No
`query`	No
`spike_min`	No
`window_hours`	No
`bucket_minutes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.7.0Sep 19, 2026
- removedInput schema / properties / bucket_minutes / default
```
Removed value: -30
```
- removedInput schema / properties / query / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / query / default
```
Removed value: -null
```
- addedInput schema / properties / query / type
```
Added value: +"string"
```
- removedInput schema / properties / spike_min / default
```
Removed value: -5
```
- removedInput schema / properties / top / default
```
Removed value: -15
```
- removedInput schema / properties / window_hours / default
```
Removed value: -6
```
First observedv0.4.3Jul 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark the tool read-only and idempotent, and the description adds meaningful behavior beyond that: it aggregates independent mentions per time bucket, computes increase versus the previous bucket, flags spikes, and includes baseline_ratio. This gives an agent a solid sense of what the tool does internally.

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 compact and well-organized: purpose statement first, then computation summary, then a clear Args list. Every sentence adds value and there is no repetition of schema or annotation fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich annotations, an output schema, and five optional parameters, the description covers the tool's core behavior, parameters, defaults, and output concepts like baseline_ratio. Nothing critical is missing for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage, but the description fully compensates by documenting all five parameters with meaning and defaults. Each parameter's role is explained, including the conditional behavior of query and top.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: it returns time-bucket flows and velocity of per-stock Telegram mentions, with increase rates and spike flags. It does not explicitly differentiate from siblings like telegram_momentum or telegram_trending, but the velocity/spike focus is reasonably distinct.

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?

The description provides parameter-level defaults and behavior (e.g., query omitted returns top velocity stocks), but gives no guidance on when to choose this tool over sibling tools such as momentum, trending, or buzz_score. No exclusions or alternate conditions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.