Space Monkey Mailchimp Dashboard

Get account and quotas

sm_get_account

Read-onlyIdempotent

Introspect the API key's own account — effective tier, per-service entitlements, current hour/month quota usage and project count. Use it to check headroom or diagnose a 403/429 before retrying.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.
`tier`	No	Tier information for the enterprise account.
`error`	No	A human-readable error message detailing what went wrong.
`usage`	No	Current-hour and current-month quota usage.
`account`	No	Basic enterprise account details.
`entitlements`	No	Per-service entitlement rows defining allowed access.
`projectCount`	No	Number of projects this key can read.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 11, 2026

changedOutput schema / description

Previous value: -"Output for the sm_get_account tool. Failure payloads arrive in the same envelope as { error, message, code }."New value: +"Output for the sm_get_account tool. Failure payloads arrive in the same envelope as { error, code }."

addedOutput schema / properties / account / properties / displayName / description
```
Added value: +"Human-readable account name."
```

addedOutput schema / properties / entitlements / description

Added value: +"Per-service entitlement rows defining allowed access."

addedOutput schema / properties / projectCount / description
```
Added value: +"Number of projects this key can read."
```
addedOutput schema / properties / tier / properties / displayName / description
```
Added value: +"Human-readable tier name."
```

addedOutput schema / properties / usage / description

Added value: +"Current-hour and current-month quota usage."

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Output for the sm_get_account tool. Failure payloads arrive in the same envelope as { error, message, code }.",
+  "properties": {
+    "account": {
+      "additionalProperties": true,
+      "description": "Basic enterprise account details.",
+      "properties": {
+        "displayName": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "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"
+    },
+    "entitlements": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "isEnabled": {
+            "description": "True if the current subscription tier permits access.",
+            "type": "boolean"
+          },
+          "rateLimitHour": {
+            "description": "The hourly quota boundary for this service.",
+            "type": "integer"
+          },
+          "rateLimitMonth": {
+            "description": "The monthly quota boundary for this service.",
+            "type": "integer"
+          },
+          "service": {
+            "description": "The name of the service this entitlement governs.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "A human-readable error message detailing what went wrong.",
+      "type": "string"
+    },
+    "projectCount": {
+      "type": "integer"
+    },
+    "tier": {
+      "additionalProperties": true,
+      "description": "Tier information for the enterprise account.",
+      "properties": {
+        "displayName": {
+          "type": "string"
+        },
+        "id": {
+          "description": "A varchar tier identifier, typically free/starter/pro/enterprise.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "usage": {
+      "additionalProperties": true,
+      "properties": {
+        "limitHour": {
+          "description": "Maximum requests allowed per hour.",
+          "type": "integer"
+        },
+        "limitMonth": {
+          "description": "Maximum requests allowed per month.",
+          "type": "integer"
+        },
+        "resetHour": {
+          "description": "UTC Unix epoch seconds when the hourly limit resets.",
+          "type": "integer"
+        },
+        "resetMonth": {
+          "description": "UTC Unix epoch seconds when the monthly limit resets.",
+          "type": "integer"
+        },
+        "usedHour": {
+          "description": "Requests utilized in the current hour window.",
+          "type": "integer"
+        },
+        "usedMonth": {
+          "description": "Requests utilized in the current month window.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior Mend. The description adds valuable context by revealing what specific account data is inspected and by tying the tool to quota/error diagnosis, which helps the agent anticipate the nature of the response and the practical use case.

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?

Two sentences, each earning its place. The first describes what the tool returns, and the second gives actionable guidance on when to use it. No filler, no repetition of schema or annotation information.

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?

For a zero-parameter, read-only introspection tool with rich annotations and an output schema, the description is complete. It covers what data is returnedaine, why an agent would call it, and how to interpret its role in retry/error handling. Nothing needed to invoke it correctly is missing.

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 and the schema is fully documented as an empty object, so parameter semantics are trivially satisfied. The description reinforces that the tool introspects the API key's own context, which further removes any ambiguity about what the agent needs to pass.

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 states a specific verb ('Introspect'), a precise resource ('the API key's own account'), and concrete data returned (effective tier, per-service entitlements, quota usage, project count). It clearly distinguishes itself from the sibling sm_get_* tools by scoping to the caller's own account rather than campaigns, members, projects, or sync runs.

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 gives explicit use cases: checking headroom and diagnosing 403/429 errors before retrying. It does not name alternatives or explicitly say when not to use it, but the self-account scope and quota focus provide enough context for an agent to select this tool versus the get/list siblings.

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?