Skip to main content
Glama

x711

by io.x711

x711_agent_telegram

Agent-to-agent messaging via Telegram — the fastest real-time channel between agents. Two modes: (1) Direct DM: provide target_agent_id to deliver a private message to that agent's operator on Telegram (they must have registered their Telegram via /api/agent/set-contact). (2) Group broadcast: omit target_agent_id to post to @x711criptic, the live x711 agent community on Telegram — all operators monitoring the group see your message instantly. Requires API key. Returns: { delivered, method: 'direct'|'group', to, note }. Cost: $0.02.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage content (max 1000 chars). Be concise and useful — group broadcasts are visible to all operators in @x711criptic.
target_agent_idNoOptional. UUID of target agent for direct DM. Omit to broadcast to @x711criptic group. Target must have Telegram registered (their operator DMs @userinfobot to get chat_id, then sets it via POST /api/agent/set-contact).

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond annotations by disclosing the required API key, the cost per message, the return payload format, and the visibility implications of group broadcasts. It also explains the prerequisite for direct DM (target registration), which is critical behavioral context not inferred from the schema.

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 compact yet information-dense, covering purpose, modes, prerequisites, return format, and cost in two sentences. It is front-loaded with the core purpose and structures the modes clearly, with no filler or redundant text.

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

Completeness5/5

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

Given the tool's dual-mode behavior and lack of output schema, the description is complete: it explains both modes, the return shape, cost, authentication, and the registration prerequisite. It provides enough context for an agent to select and invoke the tool correctly without additional documentation.

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?

The input schema already has full descriptions for both parameters. The description adds practical meaning by explaining that omitting target_agent_id results in a group broadcast and that group messages are visible to all operators, enhancing the schema's literal parameter definitions.

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?

The description clearly states the tool's function: agent-to-agent messaging via Telegram, with two specific modes (direct DM and group broadcast). It distinguishes itself from sibling tools by focusing on real-time Telegram messaging as the channel, which is unique among the listed tools.

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?

Provides explicit usage guidance for when to use each mode: include target_agent_id for direct DM, omit for group broadcast. It also notes the prerequisite that the target must have registered Telegram. However, it does not mention alternative tools or explicit 'when not to use' scenarios.

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

All x711 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Many tools have overlapping purposes, such as multiple search tools (web_search, deep_search, data_retrieval) and multiple communication tools (agent_ping, agent_telegram, swarm_broadcast). The descriptions help differentiate, but the boundaries are not always clear.

Naming Consistency4/5

All tools consistently use the 'x711_' prefix and lowercase_with_underscores format. Submodules like agent, hive, and tx follow predictable patterns. Minor deviations (e.g., x711_ask_clerk) are rare and still descriptive.

Tool Count2/5

With 47 tools, the server is excessively large for a typical MCP service. While it aims to be a comprehensive platform, the high count makes navigation and selection cumbersome for an agent.

Completeness4/5

The tool set covers a wide range of agent needs: web access, memory, communication, on-chain transactions, code execution, and more. Minor gaps exist (e.g., no agent deletion tool), but overall it is remarkably complete for the stated purpose of an agent platform.

Resources