Skip to main content
Glama
AgenticMail

AgenticMail

Official
by agenticmail

telegram_poll

Pulls and processes new Telegram updates in poll mode so agents can ingest inbound messages and answer operator questions on a schedule.

Instructions

Pull and process new Telegram updates (poll-mode transport). Call this on a schedule when the channel is in poll mode to ingest new inbound messages and answer ask_operator questions sent from the operator chat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "telegram_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
_accountNoOptional. Override identity for THIS call: pass the AgenticMail agent name (e.g. "Fola") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.104
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.9.101
  3. Removedv0.9.89
  4. Addedv0.9.73
  5. Removedv0.9.69
  6. Addedv0.9.63

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 usefully discloses that this is not a pure read: it ingests inbound messages and also 'answers ask_operator questions', implying outbound side effects. However, it says nothing about idempotency, how already-processed updates are handled, failure/retry behavior, or what the call returns, which matters for a scheduled ingestion loop.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core action front-loaded and the scheduling guidance second. No filler, though the trailing clause about answering operator questions is slightly long-winded relative to the information it carries.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description is the only source of behavioral detail. It covers the what and the when adequately, but omits return shape, update-tracking semantics, and side effects on the operator chat, leaving real gaps for a scheduled ingestion tool.

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?

There is only one optional parameter (_account) and its schema description is complete (100% coverage), so the schema does the work. The description adds no meaning about identity override or authentication implications, so 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?

The description gives a specific verb and resource ('Pull and process new Telegram updates') and pins the transport mode ('poll-mode transport'), which separates it from the send/config siblings. It does not explicitly name a sibling to contrast with, so it stops just short of full differentiation.

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

Usage Guidelines4/5

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

'Call this on a schedule when the channel is in poll mode' states a clear triggering condition and cadence, which is exactly the context an agent needs. It does not state when NOT to use it (e.g., webhook mode) or what happens if called out of band, but the positive guidance is unambiguous.

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