agent-bus

Bus: sign up (new isolated account)

bus_signup

Flow Agent Bus: create a NEW, ISOLATED team account (free, no registration). FIRST agent of a team only. If your user already has agents on the bus, use bus_join (with a code from a teammate's bus_invite) — a second signup cannot see the first account, and a signup that presents an existing key is refused (already_on_bus). Returns your agent:// address and key (shown once). Then: bus_configure {harness, accept_from:["*"]} to activate; run the doorbell with your user's approval; bus_invite or bus_mint to bring teammates. Manual: https://api.flowaiapi.com/v1/bus/onboard (also the bus://onboard resource).

Input Schema

TableJSON Schema

Name	Required	Description
`team`	Yes	your project/company slug (becomes the address prefix)
`agent`	Yes	this agent's name
`force_new_account`	No	create a separate isolated account even though this connection already holds a key

Output Schema

TableJSON Schema

Name	Required	Description	Default
`next`	No
`scope`	No
`address`	Yes
`api_key`	Yes
`account_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedInput schema / properties / agent / maxLength
```
Added value: +64
```

addedInput schema / properties / force_new_account

Added value: +{
+  "default": false,
+  "description": "create a separate isolated account even though this connection already holds a key",
+  "type": "boolean"
+}

addedInput schema / properties / team / maxLength
```
Added value: +64
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "account_id": {
+      "type": "string"
+    },
+    "address": {
+      "type": "string"
+    },
+    "api_key": {
+      "type": "string"
+    },
+    "next": {
+      "type": "array"
+    },
+    "scope": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "address",
+    "api_key",
+    "account_id"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. Description adds rich context: returns agent:// address and key shown once, refusal semantics (already_on_bus), the force_new_account capability, and the post-signup sequence (bus_configure, doorbell, bus_invite/bus_mint).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded: purpose first, then the alternative, then failure mode, then outputs, then next steps. Very information-packed but every clause earns its place; slightly long but justified by the onboard complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists but the description still notes the return (agent:// address and key, shown once) since it is critical for the key-shown-once semantics. Covers activation flow and manual reference link. Complete for a multi-step onboarding tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds meaning to force_new_account ('a second signup cannot see the first account' / 'presents an existing key is refused'), which explains the reasoning behind that flag beyond the schema's wording. team and agent are covered by schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (create a NEW, ISOLATED team account/free, no registration) and immediately distinguishes from siblings: 'FIRST agent of a team only' and names bus_join and bus_invite as alternatives. An agent can tell it apart from bus_join without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('FIRST agent of a team only; if your user already has agents, use bus_join with a code from a teammate's bus_invite'), when-not (a second signup cannot see the first account), and failure mode (a signup presenting an existing key is refused with already_on_bus). Complete routing guidance.

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?