Cleotic

Get plan

get_plan

Read-onlyIdempotent

Read the organisation's plan: limits and their use (null limit = unlimited), included features, the Content Studio generation allowance, the model budget, and the AI models every segment collects from. Check it before a write that costs plan capacity, a generation, or model budget.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`generated_at`	Yes	RFC 3339 time the response was made.
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedOutput schema / properties / data / properties / plan / description

Previous value: -"trial, starter, business, enterprise, or custom."New value: +"trial, starter, business, or custom."

Changed1 schema field changedOct 1, 2026
- addedOutput schema / properties / data / properties / limits / items / properties / used / description
```
Added value: +"What is in use. For segments_per_brand, the most segments any one brand has."
```

Changed2 schema fields changedOct 1, 2026

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "content_studio_generations": {
+          "additionalProperties": false,
+          "description": "Drafts and outreach Content Studio can write this period.",
+          "properties": {
+            "limit": {
+              "description": "null when unlimited.",
+              "type": [
+                "null",
+                "integer"
+              ]
+            },
+            "remaining": {
+              "description": "null when unlimited.",
+              "type": [
+                "null",
+                "integer"
+              ]
+            },
+            "resets_at": {
+              "type": "string"
+            },
+            "used": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "limit",
+            "used",
+            "remaining",
+            "resets_at"
+          ],
+          "type": "object"
+        },
+        "features": {
+          "description": "Features the plan includes.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "history_days": {
+          "description": "How far back answers can be read; null when unlimited.",
+          "type": [
+            "null",
+            "integer"
+          ]
+        },
+        "limits": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "limit": {
+                "description": "null when unlimited.",
+                "type": [
+                  "null",
+                  "integer"
+                ]
+              },
+              "remaining": {
+                "description": "null when unlimited.",
+                "type": [
+                  "null",
+                  "integer"
+                ]
+              },
+              "resource": {
+                "type": "string"
+              },
+              "used": {
+                "type": "integer"
+              }
+            },
+            "required": [
+              "resource",
+              "limit",
+              "used",
+              "remaining"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "models": {
+          "description": "The AI models every segment collects from on this plan.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "model": {
+                "description": "Model family key.",
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "model",
+              "name"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "monthly_model_budget_usd": {
+          "description": "Monthly AI model spend allowed; null when unlimited.",
+          "type": [
+            "null",
+            "integer"
+          ]
+        },
+        "plan": {
+          "description": "trial, starter, business, enterprise, or custom.",
+          "type": "string"
+        },
+        "subscription": {
+          "additionalProperties": false,
+          "description": "Set when the plan is billed by subscription.",
+          "properties": {
+            "cancel_at_period_end": {
+              "type": "boolean"
+            },
+            "interval": {
+              "type": "string"
+            },
+            "renews_at": {
+              "type": "string"
+            },
+            "status": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "status",
+            "interval",
+            "renews_at",
+            "cancel_at_period_end"
+          ],
+          "type": [
+            "null",
+            "object"
+          ]
+        },
+        "trial": {
+          "additionalProperties": false,
+          "description": "Set on a trial.",
+          "properties": {
+            "days_remaining": {
+              "type": "integer"
+            },
+            "expires_at": {
+              "type": "string"
+            },
+            "state": {
+              "description": "active or expired.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "state",
+            "expires_at",
+            "days_remaining"
+          ],
+          "type": [
+            "null",
+            "object"
+          ]
+        }
+      },
+      "required": [
+        "plan",
+        "trial",
+        "subscription",
+        "limits",
+        "features",
+        "content_studio_generations",
+        "monthly_model_budget_usd",
+        "history_days",
+        "models"
+      ],
+      "type": "object"
+    },
+    "generated_at": {
+      "description": "RFC 3339 time the response was made.",
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "generated_at",
+    "data"
+  ],
+  "type": "object"
+}

AddedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description goes beyond them by decoding a data semantic an agent cannot infer: 'null limit = unlimited'. It doesn't discuss freshness/caching of plan data, but the added interpretation earns a 4.

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?

Two sentences, no filler; the content inventory comes first and the usage trigger second, so it is front-loaded correctly. The colon-separated inventory is slightly dense but every item listed is a distinct part of the response and 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?

With an output schema present, the description is not obliged to describe return values, and it correctly spends its words on what the plan object covers and when checking it matters. Nothing an agent needs in order to call this zero-argument read tool 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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No misleading parameter language is present.

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?

States a specific verb (Read) and resource (the organisation's plan), then enumerates exactly what the payload contains: limits and their use, included features, generation allowance, model budget, and collected models. That enumeration cleanly separates it from neighbours like get_brand_settings and get_brand_overview without the agent opening any schema.

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 concrete trigger: 'Check it before a write that costs plan capacity, a generation, or model budget.' That is a real when-to-use condition rather than generic filler. It stops short of naming an alternative or an explicit when-not, so it lands just under the top band.

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

All Cleotic 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?