Mailrith Email Marketing

Get authenticated API capabilities

discovery_get_capabilities

Read-onlyIdempotent

Returns the current workspace context, discovery URLs, shared request conventions, supported webhook events, and public resource operations available to the authenticated bearer credential. Permission: none. API reference: https://mailrith.com/developers/api-reference.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`response`	No
`request_id`	Yes	The stable correlation ID for this MCP tool invocation.
`operation_id`	Yes	The stable Mailrith public API operation ID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 3, 2026

changedOutput schema / $defs / Capabilities / properties / capability_mode / description

Previous value: -"Resources contain only operations currently available to this credential, plan, workspace state, and rollout state."New value: +"Resources contain only operations currently available to this credential, plan, workspace state, rollout state, and active MCP client catalog when called through MCP."

addedOutput schema / $defs / PublicApiMcp / properties / active_operation_ids

Added value: +{
+  "anyOf": [
+    {
+      "description": "Exact operation IDs exposed by this MCP client's active tool catalog. Omitted for direct REST requests and unrestricted MCP clients.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed2 schema fields changedSep 3, 2026

changedOutput schema / $defs / Capabilities / properties / capability_mode / description

Previous value: -"Resources contain only operations currently available to this credential, plan, workspace state, rollout state, and active MCP client catalog when called through MCP."New value: +"Resources contain only operations currently available to this credential, plan, workspace state, and rollout state."

removedOutput schema / $defs / PublicApiMcp / properties / active_operation_ids

Removed value: -{
-  "anyOf": [
-    {
-      "description": "Exact operation IDs exposed by this MCP client's active tool catalog. Omitted for direct REST requests and unrestricted MCP clients.",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

Changed2 schema fields changedAug 17, 2026

changedOutput schema / $defs / Capabilities / properties / capability_mode / description

Previous value: -"Resources contain only operations currently available to this credential, plan, workspace state, and rollout state."New value: +"Resources contain only operations currently available to this credential, plan, workspace state, rollout state, and active MCP client catalog when called through MCP."

addedOutput schema / $defs / PublicApiMcp / properties / active_operation_ids

Added value: +{
+  "anyOf": [
+    {
+      "description": "Exact operation IDs exposed by this MCP client's active tool catalog. Omitted for direct REST requests and unrestricted MCP clients.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedJul 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description aligns with these and adds useful behavioral context: the data is scoped to the authenticated bearer credential and no specific permission is required. It also points to an API reference, though it does not mention rate limits or error handling.

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 a single, front-loaded sentence that immediately states what is returned, followed by two brief informative notes (permission and API reference). No filler or redundant wording. Every part earns its place.

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?

Given the tool has no parameters, has an output schema, and annotations cover safety and idempotency, the description provides sufficient context: it enumerates the exact categories of information returned and notes the zero-permission requirement. It is complete for a simple read-only discovery endpoint.

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?

The tool has zero parameters, so the schema describes everything. Baseline 4 applies because there is nothing for the description to add about parameters. The description focuses on return values rather than input semantics, which is appropriate.

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 the specific verb 'Returns' and clearly enumerates the resources returned (workspace context, discovery URLs, shared request conventions, supported webhook events, public resource operations). This distinguishes it from sibling tools like workspace_get, which likely only returns workspace context. The purpose is unmistakable.

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 guidance is given on when to use this tool versus alternatives, nor does it mention that it could serve as a discovery prelude to other API operations. The 'Permission: none' note is about auth, not usage context. There is no 'use this for...' or 'instead of...'.

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

All Mailrith Email Marketing 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.