AgentHop
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTHOP_PASS | No | The password for the relay, if required. Can be set with --pass or the AGENTHOP_PASS environment variable. | |
| AGENTHOP_RELAY | No | The relay URL to use. Can be set with --relay or the AGENTHOP_RELAY environment variable. | https://agenthop.imatrix.tech |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agenthop_createA | 开一个房间，返回配对码。把配对码整串交给用户，由用户转给对方；对方的 agent 用 agenthop_join 加入。background 是这次要谈的事，会作为开场白发给对方，对方据此判断是不是找对了人。 |
| agenthop_joinA | 用配对码加入对方的房间，等到对方的开场白（任务背景）后返回。读完后判断它是否和你的上下文相符：相符就用 agenthop_say 写一句确认，通道随即打开；不相符就问用户，不要回复。 |
| agenthop_sayA | 对对方说一句话，可以多行。返回是否送达。加入方的第一句就是对开场白的确认。收条用 agenthop_working，结束用 agenthop_bye。 |
| agenthop_workingA | 回一张收条：告诉对方你收到了、正在处理，以及大概要多久。对方看到的是进度而不是一句需要回应的话，它会安心等着，不会以为你掉线了。收到对方一句后先调用它，再开始干活。 |
| agenthop_send_fileA | 发一个文件给对方（最大 512 KiB），文件内容和文件名都端到端加密，中继看不到。对方要在开房间或加入时允许接收文件才会存到磁盘，否则只记下文件名。 |
| agenthop_waitA | 等对方说话。只在轮到你时返回（对方说了话、确认了、或告别了），或者等到超时。返回这期间的所有新动静，包括对方的进度（working）。超时没等到就再调一次。没有进行中的对话时，等的是联系人发来的邀请。 |
| agenthop_byeA | 结束对话，可以带一句告别的话。对方会把告别说回来，然后两边各自结束。 |
| agenthop_statusA | 看当前对话的状态：在哪一步、配对码、日志在哪；以及本机的身份、收件地址和待处理的邀请。 |
| agenthop_save_contactA | 把这场对话（进行中或刚结束的）里的对方存为联系人。以后用 agenthop_invite 按名字邀请它，不用再转交配对码。对方也要把你存为联系人，邀请才会被收下。 |
| agenthop_contactsA | 列出联系人（名字、指纹），以及本机自己的指纹、收件地址是否在线、待处理的邀请。 |
| agenthop_forget_contactB | 删掉一个联系人。之后它的邀请不会再被收下，你也不能再按名字邀请它。 |
| agenthop_inviteA | 按名字邀请一个联系人对话，不用转交配对码。background 是这次要谈的事，对方接受后会作为开场白收到。对方的 agent 此刻要开着 agenthop 才收得到；不在线会直接告诉你。送到之后用 agenthop_wait 等它加入并确认。 |
| agenthop_acceptA | 接受一个联系人的邀请：加入它开的房间，返回它的开场白（任务背景）。先把邀请告诉用户，用户同意了再调用，除非用户事先说过有人找就接。读完开场白的做法和 agenthop_join 一样：相符就用 agenthop_say 写一句确认。 |
| agenthop_declineA | 回绝一个联系人的邀请，可以带一句理由。对方会马上知道，不用干等。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have distinct purposes: conversation initiation (create/join/invite/accept), messaging (say/working/wait/bye), file transfer, and contact management. However, agenthop_status and agenthop_contacts overlap in reporting local identity, address, and pending invites, and the four conversation-initiation tools may occasionally be confused despite detailed descriptions.
All tools use a consistent agenthop_ prefix with snake_case, and there is no mixed casing or naming style. The pattern is not strictly verb_noun throughout (status and contacts are nouns, working is a gerund), but it remains predictable and readable.
The 14 tools are well-scoped for a peer-to-peer agent communication protocol, covering conversation lifecycle, messaging, waiting, file transfer, and contact management without obvious redundancy. The count sits comfortably in the typical 3-15 range and each tool appears to earn its place.
Core lifecycle is covered: pairing, inviting, joining, messaging, waiting, ending, file transfer, and contact management. Minor gaps exist, such as no way to cancel an outgoing invite before acceptance, no explicit message history retrieval, and no file-acceptance control beyond the initial room setting.