Skip to main content
Glama
Sign In
vscode-copilot-telegram

vscode-copilot-telegram

by weslylaboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ask_user

Send a question to the user on Telegram and wait for their reply, returning the answer text or 'timeout' if no response arrives.

Instructions

Ask the user a question on Telegram and wait for the answer.

Returns the user's answer text, or the string 'timeout' if they did not answer in time.

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": {
      "question": "<question>"
    },
    "name": "ask_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoOptional choices shown as buttons. The user may still type a free-text answer.
questionYesThe question for the user. Be specific and self-contained.
timeout_sNoSeconds to wait (default from config, 600).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well on the most important trait: the call blocks until the user answers, and the sentinel return value 'timeout' is disclosed. Remaining gaps are secondary (no mention of whether the question is queued/delivered reliably if the user is offline, or whether pending asks are cancellable), so it stops short of 5.

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 short sentences, zero waste, with the core action and blocking semantics front-loaded and the return contract placed second. Nothing is redundant or padded.

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?

An output schema exists, so the description need not enumerate return structure, and it still usefully flags the 'timeout' sentinel. Combined with full parameter documentation, an agent has enough to call this correctly; only the interaction with sibling tools and failure/offline behavior remain unaddressed.

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%, so 'question', 'options', and 'timeout_s' (including the 600s default and the free-text escape hatch on options) are already fully documented in the schema. The description adds no additional parameter meaning beyond that, which makes the baseline 3 correct.

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 states a specific verb and resource ('Ask the user a question') plus the channel ('on Telegram') and the blocking behavior ('wait for the answer'). It implicitly separates itself from the fire-and-forget sibling 'notify', but never names or contrasts that alternative explicitly.

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?

Usage is only implied: an agent can infer this is for when it needs human input mid-task. There is no explicit when-to-use/when-not-to-use statement, no guidance on preferring 'notify' for one-way messages, and no note about what happens if the agent calls this repeatedly or what the cost of blocking is.

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