Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

telegram

Read-only

Reads TELEGRAM messaging via Unipile: 1-to-1 AND group conversations. Sending is telegram_act.

op:

  • "list" (default): the conversations, newest first, in items (limit 1-100). A cursor is returned only when Unipile paginates the channel (WhatsApp does not: a full page carries truncated). Group threads are listed alongside the 1-to-1 ones (is_group, named by the group's name) and read the same way. Each 1-to-1 thread is enriched with the counterpart's name (attendee_name); with_names=False turns this enrichment off (one API call fewer).

  • "read": the messages of a thread, 1-to-1 or group (chat_id from op="list"). A message Unipile passed on without text nor attachment carries content_unavailable. Each attachment carries a source: pass it to oto_import (target="project_file") to file it, or to any tool taking a source — the server fetches the file, never through the conversation.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNolist
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
limitNo
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
cursorNo
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
chat_idNo
_accountNoCompte à OPÉRER quand plusieurs existent. `oto_identity(op='list')`.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
with_namesNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real behavior: cursor is returned only when Unipile paginates, a full page otherwise carries truncated, messages without text or attachment carry content_unavailable, and with_names=False saves one API call. Its WhatsApp aside about pagination is confusing for a Telegram tool and slightly muddies the signal.

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?

Front-loads the core statement, then uses a bulleted op breakdown so each operation is scannable. It is dense but nearly every clause carries operational meaning; the detour into WhatsApp pagination and oto_import is the one place where the text strays from the tool's own surface.

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?

With 11 parameters and no output schema, the description does the job of explaining return shape: items, cursor, truncated, is_group, attendee_name, content_unavailable, and attachment source. Nothing critical for a correct call appears missing, though error/inactive-account behavior is unaddressed.

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 coverage is 55%, so the description must carry weight, and it does: it binds op values to concrete behavior, gives limit the 1-100 range, explains cursor, ties chat_id to op="list", and explains the performance tradeoff of with_names. The underscore-prefixed context params are left entirely to the schema, which is acceptable since they are documented there.

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?

States a specific verb and resource (read Telegram messaging via Unipile, 1-to-1 and group), enumerates both operations (list, read), and explicitly separates itself from the sibling that sends, telegram_act. An agent can distinguish it from whatsapp, gmail, and slack without opening any schema.

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?

Gives clear routing: writes go to telegram_act, op="list" is the default entry point, and op="read" consumes a chat_id obtained from list. It also routes attachments to oto_import. It lacks an explicit 'do not use for X' beyond sending, so it falls just short of a 5.

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

All Tulina 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