Skip to main content
Glama
ZenonEl

herald

by ZenonEl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

inbox_status

Read-onlyIdempotent

Check buffered message volume per chat and age of oldest unprocessed item to plan a fetch range, and verify daemon heartbeat plus unarchived attention flags.

Instructions

Summarise what the capture daemon has buffered, without fetching content.

Check this before inbox_fetch: it reports volume per chat and the age of the oldest unprocessed message, so a range can be chosen deliberately. last_poll is the daemon's heartbeat - if it is hours old the daemon is down and Telegram will start dropping undelivered updates after about a day. taken_unarchived is separate from new messages. If attention_required is true, say clearly that messages were read/exported more than 24 hours ago but have not been confirmed in an archive; recover them with include_taken=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatNo
scopeNoproject
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.8.0
    • addedInput schema / properties / chat
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Chat"
+}
    • addedInput schema / properties / project
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "project",
+  "enum": [
+    "project",
+    "source",
+    "all"
+  ],
+  "title": "Scope",
+  "type": "string"
+}
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond that: it does not fetch content, last_poll acts as a daemon heartbeat, and attention_required/taken_unarchived have specific operational meanings.

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 front-loaded with the core purpose and each sentence adds distinct operational guidance. It is compact despite carrying substantial warning and recovery context.

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 no output schema, the description does a good job explaining the meaningful output fields (volume per chat, oldest age, last_poll, taken_unarchived, attention_required) and how to react to them. It loses a point because the three input parameters are left undocumented and the description does not clarify how scoping works.

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 undocumented parameters. However, it never explains chat, scope, or project, leaving their effect on the summary ambiguous. The only parameter-related hint is 'volume per chat', which is not enough.

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: 'Summarise what the capture daemon has buffered' and explicitly distinguishes itself from inbox_fetch with 'without fetching content'. This clearly separates it from the sibling tool.

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

Usage Guidelines5/5

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

Explicitly instructs the agent to 'Check this before inbox_fetch' and explains why: it reports volume and age so a fetch range can be chosen deliberately. It also gives conditional guidance for last_poll and attention_required, making when-to-use unambiguous.

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