Skip to main content
Glama
ZenonEl

herald

by ZenonEl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

send_text

Send formatted messages to Telegram with provenance metadata, using HTML or plain text, and follow project-specific writing rules for consistent output.

Instructions

Send a free-form formatted message with provenance metadata.

Call get_writing_rules(project) before composing. HTML is the default. Use raw Telegram tags: , , , , , , ,

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
agentYes
modelYes
routeNo
formatNohtml
presetNobrief
projectYes
subjectYes
reply_toNo
referenceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.8.0
    • addedInput schema / $defs
      Added value: +{
+  "InboxMessageKey": {
+    "properties": {
+      "chat_id": {
+        "title": "Chat Id",
+        "type": "integer"
+      },
+      "message_id": {
+        "title": "Message Id",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "chat_id",
+      "message_id"
+    ],
+    "title": "InboxMessageKey",
+    "type": "object"
+  }
+}
    • addedInput schema / properties / format / default
      Added value: +"html"
    • addedInput schema / properties / reply_to
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/InboxMessageKey"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • changedInput schema / required
      Previous value: -[
-  "text",
-  "project",
-  "subject",
-  "agent",
-  "model",
-  "format"
-]New value: +[
+  "text",
+  "project",
+  "subject",
+  "agent",
+  "model"
+]
  2. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / preset / default
      Added value: +"brief"
    • changedInput schema / required
      Previous value: -[
-  "text",
-  "project",
-  "subject",
-  "agent",
-  "model",
-  "format",
-  "preset"
-]New value: +[
+  "text",
+  "project",
+  "subject",
+  "agent",
+  "model",
+  "format"
+]
  3. First observedv0.3.0

TDQS

B3.3/5.0
Behavior4/5

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

With minimal annotations, the description carries the behavioral load and does so well: it discloses HTML as the default, requires raw Telegram tags rather than escaped HTML, notes the preset only controls editorial density, and imposes Telegram's 4096 visible-character limit. This goes meaningfully beyond what the schema or annotations provide.

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?

The description is dense but not bloated; every sentence adds relevant information. It front-loads the purpose and then gives practical formatting rules. It could be slightly more scannable with bulleted formatting guidance, but the current structure is reasonable for the content.

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

Completeness2/5

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

Given a complex 10-parameter input schema with 0% schema description coverage and a large sibling family, the description is incomplete. It thoroughly covers Telegram formatting behavior but fails to explain the meaning or use of several required and optional parameters, and it does not route the agent away from overlapping send-related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for 10 parameters, but it only adds meaningful semantics for preset ('editorial density') and project (via get_writing_rules). Parameters like subject, agent, model, route, reply_to, and reference remain unexplained, leaving the agent to guess their roles.

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 clear, specific action: 'Send a free-form formatted message with provenance metadata.' This is a strong verb+resource statement, but it does not explicitly distinguish send_text from siblings like send_batch, send_update, or send_client_copy, so it misses the full sibling-differentiation bar.

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 description gives concrete usage guidance: call get_writing_rules(project) before composing, use raw Telegram tags, avoid HTML entities, and respect the 4096-character limit. However, it never says when to choose this tool over alternatives such as send_batch or send_update, so the when-vs-alternatives guidance is only implied, not explicit.

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