postnext

Get plan and limits

get_plan_limits

Read-onlyIdempotent

Return the user's current subscription tier and per-tier quotas (channels, storage, AI credits, posting). Available on every plan (no AI credit cost). Call this when the user asks "what plan am I on?" or "what are my limits?", or proactively before suggesting an action that might be blocked (e.g. before create_post_draft when aiCalls is low, before schedule_post when posts.current is close to posts.limit, or before connect_channel when channel slots are near the cap).

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": "get_plan_limits"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tier`	Yes
`gated`	Yes
`isPaid`	Yes
`limits`	Yes
`isTrial`	Yes
`tierDisplayName`	Yes
`creditsAvailable`	No
`subscriptionStatus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- addedOutput schema / properties / limits / properties / posts / properties / current
```
Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
```

Changed2 schema fields changedOct 28, 2026

removedOutput schema / properties / upgradeUrl

Removed value: -{
-  "format": "uri",
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "tier",
-  "tierDisplayName",
-  "isPaid",
-  "isTrial",
-  "gated",
-  "upgradeUrl",
-  "limits"
-]New value: +[
+  "tier",
+  "tierDisplayName",
+  "isPaid",
+  "isTrial",
+  "gated",
+  "limits"
+]

Changed1 schema field changedOct 2, 2026
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedSep 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish a safe read-only, idempotent, closed-world operation, so the description only needs to add context — and it does, disclosing that the call is available on every plan and costs no AI credits, which matters because it recommends calling this before AI-consuming actions. It does not discuss rate limits or caching, but nothing critical is missing for a read-only lookup.

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?

Purpose is front-loaded in the first clause, with the cost note second and the usage triggers after. The parenthetical examples are long, but each maps to a distinct precondition, so they earn their space; only mild trimming would help.

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?

With no inputs and an output schema present, the description only has to cover purpose, cost, and when to call — all present. The one gap is not positioning it against get_plan, which an agent may just as easily pick from the sibling list.

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?

Zero parameters, so there is no parameter semantics to explain; the schema already forbids additional properties. Baseline 4 applies since nothing needs compensating.

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 ('Return the user's current subscription tier and per-tier quotas') and enumerates the quota categories covered. Clear on its own, but it never distinguishes itself from the sibling get_plan, which plausibly overlaps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the user utterances that should trigger a call and adds a proactive-call pattern with three concrete preconditions (before create_post_draft, schedule_post, connect_channel) tied to specific limit fields. Almost no inference is left to the agent.

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

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