Conduit Agentic Commerce

Notify org members

agent_notify

Idempotent

Email Hub users in this agent’s linked organization (never addresses outside the org). to=all or { user_id } / { role } / { email } matching agent_organization members. Optional actions (Hub URLs only), severity, idempotency_key. Channel is email.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Who to notify: "all", { user_id }, { user_ids }, { role }, { roles }, or { email } matching an org member. Never an address outside the org.
`body`	Yes	Plain-text body, max 4000 characters. Conduit wraps HTML; do not send markup.
`title`	Yes	Subject line, max 120 characters
`actions`	No	Optional buttons, max 3. Hosts outside Conduit are rejected.
`channel`	No	Delivery channel. Email only — omit or pass email
`dry_run`	No	If true, resolve recipients and from-address without sending or storing
`agent_id`	Yes	Linked agent sending the message
`order_id`	No	Optional order correlation
`severity`	No	info (default), warning, or urgent — affects subject prefix and accent
`search_id`	No	Optional search correlation
`session_token`	No	Session token from agent_authenticate — required whenever agent_id is passed
`idempotency_key`	No	Replay key — same agent + key returns the original notify_id without sending again

Output Schema

TableJSON Schema

Name	Required	Description	Default
`from`	No
`hint`	No
`next`	No
`error`	No
`detail`	No
`failed`	No
`channel`	No
`dry_run`	No
`delivered`	No
`notify_id`	No
`recipients`	No
`idempotent_replay`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026
- addedOutput schema / properties / next / properties / args / additionalProperties / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
```
- removedOutput schema / properties / next / properties / args / additionalProperties / type
```
Removed value: -"string"
```
Changed2 schema fields changedAug 29, 2026
- removedOutput schema / properties / idempotentReplay
```
Removed value: -{
-  "type": "boolean"
-}
```
- addedOutput schema / properties / idempotent_replay
```
Added value: +{
+  "type": "boolean"
+}
```
AddedAug 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already convey mutation, idempotency, and non-destructiveness. The description adds meaningful behavioral constraints beyond those flags: delivery is email-only, recipients are restricted to org members, and action URLs must be Hub URLs. This reveals side-effects and safety boundaries not visible from annotations alone.

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

Conciseness5/5

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

The description is very concise: it front-loads the most important constraint (org-only email) and compresses recipient modes, optional fields, and channel into dense, useful phrases. No wasted words or repetition of schema details.

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?

Despite 12 parameters and 4 required fields, the description plus the fully-described schema and annotations cover the critical decision factors: who can be notified, how, via what channel, and with what URL restrictions. An output schema exists, so return values need not be explained, and dry_run/session_token behavior is already documented in the schema.

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 description coverage is 100%, so the baseline is 3. The description adds value by summarizing the polymorphic 'to' selector ('all' or user_id/role/email), clarifying the org-membership constraint, and noting optional action URL restrictions. This goes slightly beyond what the schema already states.

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 uses a specific action ('Email Hub users') and a precise scope ('this agent’s linked organization'), immediately distinguishing the tool from generic notify or outreach tools. It also reinforces key restrictions like 'never addresses outside the org.'

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?

It clearly establishes the intended context: email delivery to linked-org members only, and states channel and recipient-address restrictions. It does not explicitly name sibling alternatives such as agent_outreach or state when not to use this tool, so it stops short of full exclusion guidance.

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

All Conduit Agentic Commerce 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?