Skip to main content
Glama
Sign In

Telegram MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Telegram Prompts

prompts_menu
Read-only

Browse the Telegram prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

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": {
      "request": "<request>"
    },
    "name": "prompts_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
is_customNo
prompt_idNo
prompt_typeNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context about workspace prompts requiring is_custom=True plus workspace_id, but it does not discuss pagination, rate limits, auth, or other behavioral details beyond what annotations and output schema provide.

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 short, front-loaded with the overall purpose, and uses a numbered list to separate the two request modes. Every sentence adds useful invocation guidance without filler.

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?

Given five parameters with 0% schema description coverage, the description covers the key conditional usage patterns needed to call the tool correctly. The existence of an output schema means return values need not be documented, though prompt_type remains somewhat under-specified.

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?

Schema description coverage is 0%, so the description must explain parameter meaning, and it does so for most parameters: request modes, prompt_id for details, workspace_id and prompt_type for menu, and is_custom for workspace prompts. It could still say more about prompt_type values and validation rules, but it substantially compensates for the schema's lack of descriptions.

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 the verb and resource: browsing the Telegram prompt catalog and fetching prompt details. It explains the two request modes, making the tool's purpose understandable, though it does not explicitly contrast against sibling tools like query_contexts or query_data.

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

Usage Guidelines3/5

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

The description gives mode-specific guidance for request='menu' versus request='prompt_details', including which optional parameters to pass. However, it does not state when to use this tool versus alternatives, nor does it include exclusions or prerequisites beyond the workspace note.

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

All Telegram MCP by InsightfulPipe 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