Space Monkey Mailchimp Dashboard

Get analyst knowledge

sm_get_knowledge

Read-onlyIdempotent

Returns Space Monkey's MCP knowledge documents (analyst preamble, metric guardrails, live OpenAPI schema URL) as tool output for clients that cannot read MCP resources — read this before interpreting any Space Monkey metrics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_get_knowledge"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No	Optional short topic selector to fetch a single knowledge document (one of: analyst-preamble, metric-guardrails, openapi, faq). Omit this parameter to receive a compact topic index.

Output Schema

Name	Required	Description
`uri`	No	MCP resource URI for the knowledge document or topic.
`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.
`text`	No	Full rendered text of the enclosing document or prompt.
`error`	No	A human-readable error message detailing what went wrong.
`title`	No	Human-readable title for the enclosing item.
`topic`	No	Topic key, or null when the request did not match a single topic.
`topics`	No	Available knowledge topics.
`version`	No	Version string for the enclosing catalog or document.
`description`	No	Human-readable description of the enclosing item.
`lastUpdated`	No	ISO 8601 instant

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / topic / description

Previous value: -"Optional short topic selector to fetch a single knowledge document (one of: analyst-preamble, metric-guardrails, openapi, faq). Omit this parameter to receive every knowledge document."New value: +"Optional short topic selector to fetch a single knowledge document (one of: analyst-preamble, metric-guardrails, openapi, faq). Omit this parameter to receive a compact topic index."

removedOutput schema / properties / documents

Removed value: -{
-  "description": "Knowledge documents matching the request.",
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "description": {
-        "description": "Document description.",
-        "type": "string"
-      },
-      "text": {
-        "description": "Document body text.",
-        "type": "string"
-      },
-      "title": {
-        "description": "Document title.",
-        "type": "string"
-      },
-      "topic": {
-        "description": "Topic key the document belongs to.",
-        "type": "string"
-      },
-      "uri": {
-        "description": "Resource URI for the document.",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

Changed2 schema fields changedSep 21, 2026

changedInput schema / properties / topic / description

Previous value: -"Optional short topic selector to fetch a single knowledge document (one of: analyst-preamble, metric-guardrails, openapi). Omit this parameter to receive every knowledge document."New value: +"Optional short topic selector to fetch a single knowledge document (one of: analyst-preamble, metric-guardrails, openapi, faq). Omit this parameter to receive every knowledge document."

changedInput schema / properties / topic / enum

Previous value: -[
-  "analyst-preamble",
-  "metric-guardrails",
-  "openapi"
-]New value: +[
+  "analyst-preamble",
+  "metric-guardrails",
+  "openapi",
+  "faq"
+]

Changed19 schema fields changedSep 11, 2026
- changedOutput schema / description
```
Previous value: -"Knowledge document(s) with version and lastUpdated metadata. Failure payloads arrive in the same envelope as { error, message, code }."New value: +"Knowledge document(s) with version and lastUpdated metadata. Failure payloads arrive in the same envelope as { error, code }."
```
- addedOutput schema / properties / description / description
```
Added value: +"Human-readable description of the enclosing item."
```
- addedOutput schema / properties / documents / description
```
Added value: +"Knowledge documents matching the request."
```
- addedOutput schema / properties / documents / items / properties / description / description
```
Added value: +"Document description."
```
- addedOutput schema / properties / documents / items / properties / text / description
```
Added value: +"Document body text."
```
- addedOutput schema / properties / documents / items / properties / title / description
```
Added value: +"Document title."
```
- addedOutput schema / properties / documents / items / properties / topic / description
```
Added value: +"Topic key the document belongs to."
```
- addedOutput schema / properties / documents / items / properties / uri / description
```
Added value: +"Resource URI for the document."
```
- addedOutput schema / properties / text / description
```
Added value: +"Full rendered text of the enclosing document or prompt."
```
- addedOutput schema / properties / title / description
```
Added value: +"Human-readable title for the enclosing item."
```
- addedOutput schema / properties / topic / description
```
Added value: +"Topic key, or null when the request did not match a single topic."
```
- addedOutput schema / properties / topics / description
```
Added value: +"Available knowledge topics."
```
- addedOutput schema / properties / topics / items / properties / description / description
```
Added value: +"Topic description."
```
- addedOutput schema / properties / topics / items / properties / name / description
```
Added value: +"Topic name."
```
- addedOutput schema / properties / topics / items / properties / title / description
```
Added value: +"Topic title."
```
- addedOutput schema / properties / topics / items / properties / topic / description
```
Added value: +"Topic key."
```
- addedOutput schema / properties / topics / items / properties / uri / description
```
Added value: +"Resource URI for the topic."
```
- addedOutput schema / properties / uri / description
```
Added value: +"MCP resource URI for the knowledge document or topic."
```
- addedOutput schema / properties / version / description
```
Added value: +"Version string for the enclosing catalog or document."
```

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Knowledge document(s) with version and lastUpdated metadata. 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"
+    },
+    "description": {
+      "type": "string"
+    },
+    "documents": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "text": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "topic": {
+            "type": "string"
+          },
+          "uri": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "A human-readable error message detailing what went wrong.",
+      "type": "string"
+    },
+    "lastUpdated": {
+      "description": "ISO 8601 instant",
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "topic": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topics": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "topic": {
+            "type": "string"
+          },
+          "uri": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "uri": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the lighter bar applies. The description adds genuine context by explaining it exists as a fallback for clients lacking resource-read support, which the annotations do not convey.

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?

A single front-loaded sentence with a parenthetical enumeration and an em-dash clause that carries the usage trigger. Dense but every clause earns its place; only slightly run-on.

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?

An output schema exists, so return format needn't be restated, and annotations already cover the safety profile. Purpose, contents, and the usage trigger are all present, leaving only minor gaps around the parametrized topic fetch.

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% and the single optional 'topic' enum is fully documented upstream, so the baseline of 3 applies. The description names three of the four topics but omits 'faq' and never mentions the omit-to-get-index behavior, adding little beyond the schema.

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?

States a specific verb and resource ('Returns ... knowledge documents') and enumerates the payload (analyst preamble, metric guardrails, OpenAPI schema URL), so an agent knows exactly what comes back. It does not explicitly contrast itself with nearby siblings like sm_get_prompt or sm_get_schema, which keeps it short of a 5.

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?

Gives a clear trigger ('read this before interpreting any Space Monkey metrics') and a scope condition ('for clients that cannot read MCP resources'), implicitly routing resource-capable clients elsewhere. It stops short of naming a specific alternative tool or stating when-not to call it in more absolute terms.

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?