Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

telegram_bot

Read-only

Get a public Telegram bot's profile and return its name, verified flag, description, avatar link and monthly user count (zero when Telegram does not show it). Use this to size up a bot or mini app; a channel, group, person's account or invite link returns an error naming the right tool, and an unknown username returns not found.

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": {
      "username": "<username>"
    },
    "name": "telegram_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesBot username, with or without a leading @ or a t.me URL prefix

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With readOnlyHint and openWorldHint already present, the description adds meaningful behavior beyond annotations: the exact profile fields returned, the fallback to zero when monthly users are hidden, the error behavior for non-bot inputs, and the not-found behavior for unknown usernames.

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, front-loaded with the operation and return fields, followed by usage and error behavior. No sentence is wasted.

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 description is complete for a single-parameter read tool: it covers purpose, returned fields, fallback values, invalid input types, and unknown usernames. An output schema exists, and the description still provides useful return-field context without over-explaining.

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 description coverage is 100%, and the schema already documents that the username may include a leading @ or t.me URL prefix. The description adds no further parameter detail, so baseline 3 is appropriate.

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 and resource: get a public Telegram bot's profile. It enumerates the returned fields (name, verified flag, description, avatar link, monthly user count), which distinguishes it from sibling tools like telegram_channel, telegram_group, and telegram_post.

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 says to use this to size up a bot or mini app, and explicitly states what happens for other entity types: channels, groups, personal accounts, and invite links return an error naming the right tool. It also specifies the unknown-username 'not found' outcome, giving clear when-to-use and when-not-to-use guidance.

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

All Crawlora MCP 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