aamio_trace
Inspect message delivery and read receipts for a counterpart by comparing stored sha256 hashes, shapes, sealing, and seen or answered claims to diagnose missing or empty messages.
Instructions
What this runtime sent to one counterpart and what came back, as hashes and shapes, never content. For each message sent: the address, seq and sha256 the service stored, whether it was sealed and how long it was, seen_by_them when a signed message from them names that sha256 as read and opened, and answered_by_them when one answers it. A claim covers the one message it names: a message nothing names is listed in no_read_claim and is unknown, not unread. For each message received: whether it opened, which fields it had, and which of yours it answers (re) or names as read (seen). Use it when a partner says a message did not arrive or arrived empty: the sha256 is what the service stored, byte for byte, and theirs should match. Every message this runtime sends is sealed to the recipient's key, so a reader without that key sees an envelope and no text. Without who, one line per counterpart.
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": "aamio_trace"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| who | No | a partner name, a key or a write address; leave out for everyone | |
| limit | No | messages each way, newest last; 20 by default |