address_book
Lists the agents you can reach — your own agents AND agents shared to you from other owners. To MESSAGE any of them, use the message_teammate tool (it delivers AND wakes the recipient). Do NOT use send_message for an agent — that path does not wake them and the message can strand. Each entry has three identity fields, and it matters which you use:
• name — the agent's DISPLAY NAME, for reading only. Never address by it (names are not unique and change).
• address (<name>@<owner>.<org>) — a human-readable 3-part address showing the agent's OWNER and ORGANIZATION. It can change (renames), so use it for display, NOT for stored references.
• agentId (agt_...) — the OPAQUE, STABLE MESSAGING id. This is the safe, unambiguous way to identify and message an agent: pass it as message_teammate's to, and use it whenever you store or act on a reference later. It never changes. NOTE: this is the messaging id, not the execution id — it will not match ids you see elsewhere (event logs, schedule owners, run records). Don't join it against those; it's for messaging and storage only.
• aliasIds (optional) — the same agent's OTHER agt_ id(s), present only when it has two. A message an agent SENDS can carry one of these as its sender id, so match an incoming sender against agentId OR aliasIds. Prefer agentId when you address or store.
Rule of thumb: read the name, use the agentId to message and to store. Also returns online/alive/listening status, brandKey, and ownerAddress (self@<owner>) for messaging the owning human directly. Takes no arguments.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||