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

vscode-copilot-telegram

by weslylaboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notify

Sends a one-way status update to a user's Telegram so they can receive progress or alert messages without waiting for a reply.

Instructions

Send a one-way status message to the user's Telegram (does not wait for a reply).

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": {
      "message": "<message>"
    },
    "name": "notify"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesShort status update for the user.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the delivery channel (Telegram) and the non-blocking, one-way nature, which is genuine value. It omits message length limits, formatting support, failure/undeliverable behavior, and any rate limits — gaps that matter for a send operation.

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?

One sentence, front-loaded with the action and channel, with the non-obvious async behavior attached in parentheses. No wasted wording.

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?

For a one-parameter notification tool with an output schema covering return values, this is close to sufficient — the channel and non-blocking behavior are the essentials. Delivery constraints and failure semantics remain unaddressed, which is a minor but real gap.

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 coverage is 100% with a single required 'message' parameter already documented as a short status update. The description reinforces the one-way status framing but adds no syntax, length, or formatting guidance beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Send a one-way status message to the user's Telegram') and adds the key qualifier that it does not wait for a reply. That qualifier implicitly separates it from a reply-awaiting sibling, but no sibling is named, so differentiation is inferred rather than explicit.

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 parenthetical 'does not wait for a reply' implies the right context: fire-and-forget status updates where no response is needed. However, it never says when to prefer this over alternatives or that replies require a different tool, leaving the agent to infer usage.

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