get_planRead the organisation's plan: limits and their use (null limit = unlimited), included features, the Content Studio 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.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| generated_at | Yes | RFC 3339 time the response was made. | |
| schema_version | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / data / properties / plan / descriptionPrevious value: -"trial, starter, business, enterprise, or custom."New value: +"trial, starter, business, or custom."Output schema / properties / data / properties / limits / items / properties / used / descriptionAdded value: +"What is in use. For segments_per_brand, the most segments any one brand has."Input schema / additionalPropertiesAdded value: +falseOutput 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real interpretive context beyond that, notably the 'null limit = unlimited' convention and the fact that it exposes per-segment model collection. Not a rich behavioral narrative, but a useful increment over the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the resource and the contents, then the when-to-use trigger. Dense but every clause carries information. The enumerated contents list is slightly long but each item is a distinct capability of the plan object.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema already describing the return shape, the description need not restate fields, and it correctly focuses on purpose and timing. The read is fully specified for a no-parameter, annotated, schema-documented tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 schema or description to disambiguate. Baseline 4 applies; the description cannot add parameter meaning where none exists.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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) and then enumerates exactly what is returned: limits and their use, included features, Content Studio allowance, model budget, and per-segment AI models. No sibling tool reads plan data, so it is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to call it: 'before a write that costs plan capacity, a generation, or model budget.' That is clear pre-flight guidance. It does not name an alternative tool, but no sibling overlaps this concern, so the omission is minor.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.