Conduit Agentic Commerce

Update agent profile

agent_update

Patch handle, rails, default_destination (postcode required for ships-to), friendly_name, human_description, role_description, avatar (glyph+gradient or small image), business profile, or preferences. Set avatar only if the human chose it. Does not accept permissions — a human enables capabilities in Hub Agent settings.

Input Schema

TableJSON Schema

Name	Required	Description
`avatar`	No	Identity mark. Omit unless the human chose it — server assigns a random invader+gradient. { kind:"glyph", glyph:"invader"\|emoji, tint?:invader color, gradient } or { kind:"image", src }. Tint only for invader. Do not store in the credentials file.
`handle`	No	New display handle (lowercase kebab)
`agent_id`	Yes	Agent id to patch, e.g. agt_...
`preferences`	No	Preferences patch
`friendly_name`	No	Human-facing label (≠ handle), e.g. EU Restock Bot
`payment_rails`	No	Replacement rail key list
`session_token`	No	Session token from agent_authenticate — required whenever agent_id is passed
`business_profile`	No	Business profile patch
`role_description`	No	Self-instruction for this agent only, e.g. manage EU supplies
`human_description`	No	Description shown to humans on the org dashboard
`default_destination`	No	Where orders ship. postcode + country is enough for accurate search; add address, locality and region so checkout links arrive prefilled instead of blank.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`next`	No
`error`	No
`nonce`	No
`avatar`	No
`detail`	No
`handle`	No
`persist`	No
`agent_id`	No
`mandates`	No
`terminal`	No
`challenge`	No
`created_at`	No
`public_key`	No
`reputation`	No
`open_orders`	No
`permissions`	No
`preferences`	No
`organization`	No
`total_orders`	No
`friendly_name`	No
`payment_rails`	No
`organization_id`	No
`business_profile`	No
`role_description`	No
`human_description`	No
`destination_source`	No
`default_destination`	No
`effective_destination`	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"
```

Changed4 schema fields changedSep 7, 2026

addedInput schema / properties / default_destination / additionalProperties
```
Added value: +{}
```

changedInput schema / properties / default_destination / description

Previous value: -"Shipping destination; must include postcode for accurate search"New value: +"Where orders ship. postcode + country is enough for accurate search; add address, locality and region so checkout links arrive prefilled instead of blank."

addedInput schema / properties / default_destination / properties

Added value: +{
+  "address": {
+    "description": "Street address. Needed for checkout to prefill",
+    "type": "string"
+  },
+  "city": {
+    "description": "Alias of locality",
+    "type": "string"
+  },
+  "country": {
+    "description": "ISO country code, e.g. US",
+    "type": "string"
+  },
+  "email": {
+    "description": "Buyer contact email for the merchant order",
+    "type": "string"
+  },
+  "locality": {
+    "description": "City. Needed for checkout to prefill",
+    "type": "string"
+  },
+  "name": {
+    "description": "Recipient name; many merchants require it to fulfil",
+    "type": "string"
+  },
+  "phone": {
+    "description": "Buyer phone in E.164, e.g. +12125550188",
+    "type": "string"
+  },
+  "postal_code": {
+    "description": "Alias of postcode",
+    "type": "string"
+  },
+  "postcode": {
+    "description": "Postal / ZIP code. Enough for search and delivery estimates",
+    "type": "string"
+  },
+  "region": {
+    "description": "State / province",
+    "type": "string"
+  },
+  "state": {
+    "description": "Alias of region",
+    "type": "string"
+  },
+  "street_address": {
+    "description": "Alias of address",
+    "type": "string"
+  }
+}

addedInput schema / properties / default_destination / type
```
Added value: +"object"
```

Changed24 schema fields changedAug 29, 2026
- removedOutput schema / properties / agentId
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / agent_id
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / businessProfile
```
Removed value: -{}
```
- addedOutput schema / properties / business_profile
```
Added value: +{}
```
- removedOutput schema / properties / createdAt
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / created_at
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / defaultDestination
```
Removed value: -{}
```
- addedOutput schema / properties / default_destination
```
Added value: +{}
```
- removedOutput schema / properties / effectiveDestination
```
Removed value: -{}
```
- addedOutput schema / properties / effective_destination
```
Added value: +{}
```
- removedOutput schema / properties / friendlyName
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / friendly_name
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / humanDescription
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / human_description
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / openOrders
```
Removed value: -{}
```
- addedOutput schema / properties / open_orders
```
Added value: +{}
```
- removedOutput schema / properties / paymentRails
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
- addedOutput schema / properties / payment_rails
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- removedOutput schema / properties / publicKey
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / public_key
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / roleDescription
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / role_description
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / totalOrders
```
Removed value: -{}
```
- addedOutput schema / properties / total_orders
```
Added value: +{}
```

Changed3 schema fields changedAug 28, 2026

addedInput schema / properties / avatar

Added value: +{
+  "description": "Identity mark. Omit unless the human chose it — server assigns a random invader+gradient. { kind:\"glyph\", glyph:\"invader\"|emoji, tint?:invader color, gradient } or { kind:\"image\", src }. Tint only for invader. Do not store in the credentials file."
+}

addedOutput schema / properties / avatar
```
Added value: +{}
```

addedOutput schema / properties / permissions

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedAug 10, 2026

addedInput schema / properties / session_token

Added value: +{
+  "description": "Session token from agent_authenticate — required whenever agent_id is passed",
+  "type": "string"
+}

AddedJul 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate a mutating operation (readOnlyHint=false), and the description adds behavioral nuances: avatar is only set if the human chose it, server may assign a random invader+gradient, and postcode is required for ships-to destinations. These constraints go beyond the schema and align with annotations, with 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 a single, information-dense sentence that fronts the action and enumerates fields. While long, every clause adds relevant detail (e.g., avatar constraints, permissions exclusion), so it is efficient for its scope.

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

Completeness4/5

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

With 11 parameters including nested objects and an output schema, the description covers all update categories and highlights key constraints. It omits session_token requirements, but those are fully specified in the schema. This is a complete high-level guide for a patch operation.

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 each parameter is already documented. The description adds extra meaning by highlighting 'postcode required for ships-to' and the avatar selection rule, which are not explicit in the schema. It enhances comprehension without redundancy.

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 opens with a clear verb 'Patch' and an explicit list of modifiable fields (handle, rails, default_destination, friendly_name, human_description, role_description, avatar, business profile, preferences). This precisely distinguishes it from siblings like agent_create (creation), agent_authenticate (auth), and agent_notify (notification).

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 states what the tool does not accept (permissions) and directs that humans enable capabilities in Hub Agent settings, which guides an agent away from using this tool for permission changes. It doesn't name alternative tools explicitly, but the usage context is clear enough.

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?