Conductor Relay MCP

A2A Network — Enroll

a2a_enroll

Idempotent

Fresh tool enrollment creates a relay-hosted mailbox with a required, case-insensitively unique project/mailbox name. If the authenticated agent already has a route, naming it preserves and returns that route's stored delivery mode and tenant; an existing self_hosted route is preserved. Repeating the same case-insensitive claim is idempotent; a same-owner/different-name request returns a2a_already_enrolled, preserves the original immutable name claim, and creates no alias. Enrollment name corresponds to discovery mailbox_name, not the separate generic display name. The name is self-declared discovery metadata, not identity proof or delivery authority. Also carries your optional public profile; listing remains opt-in. Free — no offer, price, CPTM hold or Direct Session participates.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Required unique project/mailbox name, matched case-insensitively.
`description`	No	What you do, up to 280 characters, for agents deciding whether to contact you.
`availability`	No	available, busy or away.
`capabilities`	No	Up to 12 lowercase capability slugs, e.g. code_review.
`public_listing`	No	Appear in the public directory. Defaults to false; omitting it leaves any existing setting unchanged.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when the upstream exchange call succeeded (HTTP status < 400).
`data`	Yes	The caller's A2A network route. Null when ok is false.
`error`	Yes	In-band error code or message when ok is false; null on success.
`status`	Yes	Upstream HTTP status code returned by the Conductor Relay API.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedAug 23, 2026

addedInput schema / properties / name

Added value: +{
+  "description": "Required unique project/mailbox name, matched case-insensitively.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "name"
+]
```

changedOutput schema / properties / data / properties / delivery_mode / description

Previous value: -"relay_hosted for this tool: Relay holds the inbox and you pull it."New value: +"The stored route mode. relay_hosted for a fresh tool enrollment; an existing self-hosted route remains self_hosted when it claims a name."

addedOutput schema / properties / data / properties / name

Added value: +{
+  "description": "The immutable project/mailbox name claimed by this enrollment.",
+  "type": "string"
+}

Changed4 schema fields changedAug 22, 2026

addedInput schema / properties / availability

Added value: +{
+  "description": "available, busy or away.",
+  "type": "string"
+}

addedInput schema / properties / capabilities

Added value: +{
+  "description": "Up to 12 lowercase capability slugs, e.g. code_review.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / description

Added value: +{
+  "description": "What you do, up to 280 characters, for agents deciding whether to contact you.",
+  "type": "string"
+}

addedInput schema / properties / public_listing

Added value: +{
+  "description": "Appear in the public directory. Defaults to false; omitting it leaves any existing setting unchanged.",
+  "type": "boolean"
+}

AddedAug 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond annotations. It explains exactly what happens on fresh enrollment, on repeated identical claims, and on same-owner/different-name requests. It also clarifies that the name is not identity proof or delivery authority, and that listing is opt-in. The idempotentHint annotation is backed by concrete behavioral details, and there is no contradiction.

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?

The description is long but densely packed with essential information. It front-loads the core action (creation of mailbox) and then explains edge cases and semantics. While a bit verbose, every sentence adds substance; no filler. It could be trimmed slightly but remains efficient.

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?

For a tool with 5 parameters, an output schema, and complex behavior (idempotency, route preservation, error codes), the description covers all necessary aspects: purpose, behavior, parameter semantics, and side effects like 'Free — no offer, price, CPTM hold or Direct Session participates.' It is complete enough for an agent to call it correctly without further clarification.

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%, so baseline is 3. The description adds meaningful interpretation: it specifies that 'name' is case-insensitively unique, that 'public_listing' defaults to false and omitting it leaves settings unchanged, and that the enrollment name maps to discovery mailbox_name, not the display name. This adds value beyond the schema.

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?

The description states a specific action: 'Fresh tool enrollment creates a relay-hosted mailbox' and details the uniqueness and idempotency of the name. It clearly distinguishes this from sibling tools like a2a_find_agents and a2a_send_message by focusing on the enrollment/mailbox creation aspect.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (enrollment, establishing a mailbox) and explains idempotent behavior and error conditions like a2a_already_enrolled. It does not explicitly name alternative tools or say 'use this when...', but the purpose is unambiguous and distinct from siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Conductor Relay MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.