Courier

create_or_update_tenant

Idempotent

Create or replace a tenant. Tenants represent organizations or groups that users belong to.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tenant_id": "<tenant_id>",
      "name": "<name>"
    },
    "name": "create_or_update_tenant"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Display name for the tenant
`brand_id`	No	Brand ID to associate with this tenant
`tenant_id`	Yes	The tenant ID
`properties`	No	Custom properties for the tenant
`user_profile`	No	Default profile data for users in this tenant
`parent_tenant_id`	No	Parent tenant ID for hierarchical tenants
`default_preferences`	No	Default notification preferences applied to users in this tenant. Example: { "items": [{ "id": "topic_abc", "status": "OPTED_IN", "type": "subscription_topic" }] }

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 3, 2026

addedInput schema / properties / default_preferences / additionalProperties
```
Added value: +false
```

changedInput schema / properties / default_preferences / description

Previous value: -"Default notification preferences for users in this tenant"New value: +"Default notification preferences applied to users in this tenant. Example: { \"items\": [{ \"id\": \"topic_abc\", \"status\": \"OPTED_IN\", \"type\": \"subscription_topic\" }] }"

addedInput schema / properties / default_preferences / properties

Added value: +{
+  "items": {
+    "description": "One entry per subscription topic",
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "custom_routing": {
+          "description": "Channels this topic delivers on when has_custom_routing is true",
+          "items": {
+            "enum": [
+              "direct_message",
+              "email",
+              "push",
+              "sms",
+              "webhook",
+              "inbox"
+            ],
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "has_custom_routing": {
+          "description": "Whether custom_routing overrides the topic's default channels",
+          "type": "boolean"
+        },
+        "id": {
+          "description": "Subscription topic ID this default applies to",
+          "type": "string"
+        },
+        "status": {
+          "description": "Default status for the topic. \"REQUIRED\" prevents users from opting out",
+          "enum": [
+            "OPTED_IN",
+            "OPTED_OUT",
+            "REQUIRED"
+          ],
+          "type": "string"
+        },
+        "type": {
+          "const": "subscription_topic",
+          "description": "Always \"subscription_topic\" when provided",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "status"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedInput schema / properties / default_preferences / required
```
Added value: +[
+  "items"
+]
```
addedInput schema / properties / default_preferences / type
```
Added value: +"object"
```

First observedApr 14, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already establish that this is a mutating, idempotent, non-destructive operation. The description adds the 'create or replace' framing but does not explain what replacement does to existing tenant data, child objects, users, or preferences. It is consistent with annotations and provides some context, but the burden of detail is left to the schema.

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 two short sentences with no wasted words and the action is front-loaded. It is concise but thin, lacking operational detail that would make it truly excellent.

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

Completeness2/5

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

With 7 parameters, nested objects like default_preferences and user_profile, and no output schema, the description is incomplete. It does not clarify what 'replace' means in practice, whether updated fields are merged or reset, what the tool returns, or how existing tenant state is affected.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents the parameters. The description adds no parameter-level guidance and merely provides background context about tenants, placing it at baseline.

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

Purpose4/5

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

The description names a specific action ('Create or replace') and resource ('a tenant'), then defines what a tenant is. It clearly identifies the tool among siblings like get_tenant and delete_tenant, though it does not explicitly contrast with them.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not say when to use this tool versus alternatives such as add_user_to_tenant, update_tenant_preference, or delete_tenant, leaving the appropriate context entirely to inference.

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

All Courier 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.