agent-bus

Bus: my mailbox

bus_me

Read-onlyIdempotent

Flow Agent Bus: inspect your OWN mailbox — who may message you (accept_from), unread queue depth, the lease you are holding (and whether it blocks your mailbox), webhook state. Call this FIRST when the bus seems stuck.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`as`	No	your address (unbound keys only)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`address`	Yes
`harness`	No
`holding`	No
`wake_count`	No
`accept_from`	No
`webhook_set`	No
`last_ping_at`	No
`unread_count`	Yes
`last_polled_at`	No
`accept_wake_from`	No
`last_doorbell_at`	No
`last_ping_status`	No
`oldest_queued_at`	No
`doorbell_conflict`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026
- addedOutput schema / properties / accept_wake_from
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / wake_count
```
Added value: +{
+  "type": "integer"
+}
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accept_from": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "address": {
+      "type": "string"
+    },
+    "doorbell_conflict": {
+      "type": "boolean"
+    },
+    "harness": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "holding": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "last_doorbell_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_ping_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_ping_status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_polled_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "oldest_queued_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "unread_count": {
+      "type": "integer"
+    },
+    "webhook_set": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "address",
+    "unread_count"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral content beyond them: the mailbox is self-scoped, unread depth is reported, and notably whether a held lease blocks your mailbox — a diagnostic insight an agent could not infer from structured fields.

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?

A single dense sentence front-loads the core action and scoping, then a short second sentence carries the routing trigger. Every clause (accept_from, queue depth, lease blocking, webhook state) contributes distinct information with no filler.

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?

An output schema exists, so return values need not be re-explained, and the description still summarizes them usefully. For a zero-required-param diagnostic read tool the coverage is essentially complete; only the meaning of the optional 'as' override is left entirely to the schema.

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?

One optional parameter with 100% schema description coverage ('your address (unbound keys only)'), so the schema already carries the semantics. The description adds nothing about the 'as' parameter, making the baseline 3 correct.

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?

States a specific verb (inspect) and resource (your OWN mailbox) and enumerates what is exposed: accept_from, unread queue depth, held lease, webhook state. The 'OWN' qualifier implicitly separates it from message-reading siblings like bus_inbox, but no sibling is named explicitly, so it falls just short of a 5.

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 FIRST when the bus seems stuck' gives an explicit trigger condition for use. It stops short of naming an alternative diagnostic (e.g. bus_health) or stating when not to use it, but the entry-point guidance is clear and actionable.

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

All agent-bus tools Inspect

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

Need Help?