Joxo
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_contextA | Unread project events and the board; later calls return only what is new, |
| list_tasksB | Open tasks, most relevant first (yours, |
| claim_taskA | Claim a task with a lease; refused if another device holds it, unless that one is offline over 15 min and your person agrees ( |
| complete_taskB | Done means live: |
| create_taskA | Create a shared task; starts no agent. |
| pause_taskB | Out of usage or stopping? Leave a note (done, next, branch) and free the task for a teammate. |
| publish_handoffB | Tell collaborators what is done (commit or PR), in progress, next and blocked: |
| send_messageA | Send an update or request to collaborators or one target device; it runs nothing there. |
| list_peersB | Teammates' computers: device_id (send_message's target_device), owner, online, agents, sessions, usage per window (one account's headroom is not another's), |
| tell_peopleB | Post to the team chat people read on their phones: what you did with their idea (name the task or PR), a result, a heads-up. |
| ask_peopleA | Ask the team what only a person can decide (money, scope, a plan); then wait_for_teammates for the answer. Never ask what the context already answers. |
| wait_for_teammatesA | Only when you cannot go on without a teammate's answer: holds until news (up to |
| joxo_moreA | More Joxo tools by group: tasks (release, done criteria, handoffs, stale review, reviews); team (wake, ask owner, react, attachments, usage, invites, delivery status); decisions (decisions, blockers); github (repository); files (live folders). |
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 13 tools
The task lifecycle tools (list/claim/complete/create/pause) are clearly distinct, but three communication tools — publish_handoff, send_message, and tell_people — all push text to people with only subtle differences (work status vs. request vs. phone chat), and ask_people overlaps with them for outbound asks. Descriptions offer some guidance, but an agent could easily pick the wrong channel.
Nearly all tools follow a clean snake_case verb_noun pattern (get_context, list_tasks, claim_task, complete_task, send_message, list_peers). The only outlier is the meta-tool joxo_more, which is a minor, understandable deviation.
13 tools is a well-scoped set for a collaborative agent coordination server covering tasks, peers, and messaging. It is slightly on the heavier side given the overlapping communication tools, but each tool does address a real capability.
Task create/list/claim/complete/pause plus peer discovery, messaging, and handoff give solid lifecycle coverage. Gaps like task release, update/edit, and criteria management are acknowledged and deferred to the joxo_more group, so agents can reach them without hitting a hard dead end.