Space Monkey Mailchimp Dashboard

Get API schema catalog

sm_get_schema

Read-onlyIdempotent

Get the Enterprise API's OpenAPI-derived schema catalog. Omitting operation returns a compact index of every Enterprise API operation; passing a tool name, full path, or path suffix returns that one operation's full parameters and resolved response schemas. Use before calling an unfamiliar tool to confirm its exact fields.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operation`	No	Optional selector for one Enterprise API operation. Omit this parameter to receive a compact index of every Enterprise API operation. Pass a tool name (e.g. sm_list_leaders), a full path (e.g. /_api/public/v1/enterprise/members/detail), or a path suffix (e.g. members/detail) to receive that operation's full parameters and resolved response schemas.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	A machine-readable identifier for the error type. For the full code taxonomy, see the sm_get_schema tool or the Enterprise API OpenAPI ErrorResponse component.
`path`	No	URL path for the operation.
`error`	No	A human-readable error message detailing what went wrong.
`method`	No	HTTP method for the operation.
`toolName`	No	MCP tool wrapping the operation, or null when none.
`operation`	No	Full OpenAPI operation object.
`schemaUrl`	No	URL of the live OpenAPI document.
`components`	No	OpenAPI components object referenced by operations.
`operations`	No	Catalog entries for each Enterprise API operation.
`operationCount`	No	Number of operations catalogued.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedSep 11, 2026
- changedOutput schema / description
```
Previous value: -"Either a compact index of operations or a detailed schema for one operation. Failure payloads arrive in the same envelope as { error, message, code }."New value: +"Either a compact index of operations or a detailed schema for one operation. Failure payloads arrive in the same envelope as { error, code }."
```
- addedOutput schema / properties / components / description
```
Added value: +"OpenAPI components object referenced by operations."
```
- addedOutput schema / properties / method / description
```
Added value: +"HTTP method for the operation."
```
- addedOutput schema / properties / operation / description
```
Added value: +"Full OpenAPI operation object."
```
- addedOutput schema / properties / operationCount / description
```
Added value: +"Number of operations catalogued."
```
- addedOutput schema / properties / operations / description
```
Added value: +"Catalog entries for each Enterprise API operation."
```
- addedOutput schema / properties / operations / items / properties / description / description
```
Added value: +"Operation description."
```
- addedOutput schema / properties / operations / items / properties / method / description
```
Added value: +"HTTP method."
```
- addedOutput schema / properties / operations / items / properties / optionalParams / description
```
Added value: +"Optional parameters."
```
- addedOutput schema / properties / operations / items / properties / path / description
```
Added value: +"URL path."
```
- addedOutput schema / properties / operations / items / properties / requiredParams / description
```
Added value: +"Required parameters."
```
- addedOutput schema / properties / operations / items / properties / summary / description
```
Added value: +"Short operation summary."
```
- addedOutput schema / properties / operations / items / properties / tags / description
```
Added value: +"Operation tags."
```
- addedOutput schema / properties / operations / items / properties / toolName / description
```
Added value: +"MCP tool wrapping the operation, or null."
```
- addedOutput schema / properties / path / description
```
Added value: +"URL path for the operation."
```
- addedOutput schema / properties / schemaUrl / description
```
Added value: +"URL of the live OpenAPI document."
```
- addedOutput schema / properties / toolName / description
```
Added value: +"MCP tool wrapping the operation, or null when none."
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Either a compact index of operations or a detailed schema for one operation. Failure payloads arrive in the same envelope as { error, message, code }.",
+  "properties": {
+    "code": {
+      "description": "A machine-readable identifier for the error type. For the full code taxonomy, see the sm_get_schema tool or the Enterprise API OpenAPI ErrorResponse component.",
+      "type": "string"
+    },
+    "components": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "error": {
+      "description": "A human-readable error message detailing what went wrong.",
+      "type": "string"
+    },
+    "method": {
+      "type": "string"
+    },
+    "operation": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "operationCount": {
+      "type": "number"
+    },
+    "operations": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "method": {
+            "type": "string"
+          },
+          "optionalParams": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "path": {
+            "type": "string"
+          },
+          "requiredParams": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "toolName": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "path": {
+      "type": "string"
+    },
+    "schemaUrl": {
+      "type": "string"
+    },
+    "toolName": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this as read-only, idempotent, and non-destructive, so the bar for behavioral disclosure is lower. The description adds meaningful behavioral detail by explaining that omitting `operation` returns a compact index and passing a selector returns full parameters and resolved response schemas. This goes beyond the annotations without contradicting them.

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?

Three sentences with no filler. The most important information (what the tool returns and the two modes) is front-loaded, and the usage guidance is placed at the end as a natural conclusion. Every sentence 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 annotations, a rich output schema, and a fully documented single optional parameter, the description is complete. An agent knows when to call it, what the two modes do, and how to select a target operation. No critical behavioral or usage context is missing.

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?

The schema itself already provides 100% coverage of the single `operation` parameter, including the omission behavior and acceptable selector forms. The description largely restates this information rather than adding new meaning, so the baseline score of 3 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 names a specific verb ('Get') and resource ('Enterprise API's OpenAPI-derived schema catalog'), and clearly distinguishes this meta-tool from the many sm_get_* and sm_list_* siblings by explaining it returns schema information rather than business data. The dual-mode behavior (index vs. single operation) makes the purpose unmistakable.

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 explicitly says to use the tool 'before calling an unfamiliar tool to confirm its exact fields,' which gives clear contextual guidance. It does not explicitly enumerate when not to use it or name alternative tools, but the guidance is specific enough that an agent can infer the appropriate invocation context.

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

All Space Monkey Mailchimp Dashboard 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?