Skip to main content
Glama

Limzo Telegram Group Stats

by com.limzo
OverviewDiscussionsAdmin

Get network-wide Limzo totals

get_global_stats
Read-only

Call this for network-wide numbers across all public Telegram groups tracked by Limzo (group count, messages, active users, replies, reactions, karma — 7-day and all-time) plus durable lifetime totals (messages analyzed, members tracked, spam messages removed) and the current top groups by Limzo Score. For finding a specific group, prefer list_groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
docsNoHuman-readable API documentation.
statsYes
openapiNoMachine-readable OpenAPI document for the REST API.
top_groupsNoCurrent top public groups by Limzo Score.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / stats / properties / members_total
      Added value: +{
+  "description": "Distinct members ever tracked across all groups.",
+  "type": "integer"
+}
    • addedOutput schema / properties / stats / properties / messages_total
      Added value: +{
+  "description": "Messages analyzed across all groups, all time (durable — survives retention pruning).",
+  "type": "integer"
+}
    • addedOutput schema / properties / stats / properties / spam_removed_total
      Added value: +{
+  "description": "Spam messages removed by moderation across all groups, all time.",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Network-wide totals across all listed public groups.",
+  "properties": {
+    "docs": {
+      "description": "Human-readable API documentation.",
+      "format": "uri",
+      "type": "string"
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "openapi": {
+      "description": "Machine-readable OpenAPI document for the REST API.",
+      "format": "uri",
+      "type": "string"
+    },
+    "stats": {
+      "properties": {
+        "active_users_7d": {
+          "type": "integer"
+        },
+        "karma_7d": {
+          "type": "integer"
+        },
+        "messages_7d": {
+          "type": "integer"
+        },
+        "messages_all": {
+          "type": "integer"
+        },
+        "public_groups": {
+          "description": "Public groups in the directory.",
+          "type": "integer"
+        },
+        "reactions_7d": {
+          "type": "integer"
+        },
+        "replies_7d": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "top_groups": {
+      "description": "Current top public groups by Limzo Score.",
+      "items": {
+        "properties": {
+          "active_users_7d": {
+            "type": "integer"
+          },
+          "messages_7d": {
+            "type": "integer"
+          },
+          "plan": {
+            "enum": [
+              "free",
+              "pro",
+              "community"
+            ],
+            "type": "string"
+          },
+          "score": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ok",
+    "stats"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds useful scope context: network-wide coverage, 7-day/all-time windows, durable lifetime totals, and top groups. It does not contradict annotations. Since the output schema exists, the lack of return format description is acceptable.

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 a single, front-loaded sentence listing key outputs, followed by one concise sentence for guidance. No wasted words; every clause adds information.

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?

The tool is simple (0 params) and has an output schema. The description thoroughly covers the returned data (metrics, timeframes, totals, top groups) and provides usage context. It is complete and self-sufficient.

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

Parameters4/5

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

There are zero parameters and schema description coverage is 100% (vacuously). No parameter explanation is needed. The description adds meaning about what data is returned, which is beyond the empty 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 a specific verb ('Call this for network-wide numbers') and clearly resources ('all public Telegram groups tracked by Limzo'), with an enumerated list of metrics. It is distinct from siblings: 'For finding a specific group, prefer list_groups' explicitly differentiates it.

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 provides an explicit alternative: 'For finding a specific group, prefer list_groups.' This gives clear when-to-use/when-not-to-use guidance and names the sibling tool.

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

All Limzo Telegram Group Stats toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources