Poly-Glot AI Workspace

Get Poly-Glot subscription status

get_subscription_status

Read-only

Read the current account's access state, trial timing, subscription entitlement locks and subscription pricing. Use before gated tools or when asked about remaining access. This read-only operation never starts a trial or a charge. Eligible introductory trials begin only after an Apple subscription is explicitly authorized in the native app.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`view`	Yes
`entitlement`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026
- addedOutput schema / properties / entitlement / properties / dailyFreeRemaining
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / entitlement / properties / lastFreeSendAt
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed3 schema fields changedSep 8, 2026
- addedOutput schema / properties / entitlement / properties / compareLocked
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / entitlement / properties / dailyFreeLimit
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / entitlement / properties / nextResetAt
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond that: it states the call never starts a trial or charge, and that trials only begin after explicit Apple authorization in the native app. That guards against an agent assuming a side effect.

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?

Three sentences, each front-loaded and serving a purpose: capability, usage trigger, safety clarification. The final Apple sentence is slightly tangential but justified because it explains trial semantics an agent might otherwise misinterpret.

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?

A read-only, zero-parameter tool with an output schema, so return values need not be explained. Usage, safety, and capability are all covered, leaving nothing an agent needs to invoke it correctly.

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 the baseline is 4. The description correctly does not pad with parameter detail, and the schema is empty by design.

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 ('current account's access state'), then enumerates what is returned: trial timing, entitlement locks, and pricing. Although siblings are unrelated language tools, the definition leaves no ambiguity about what this call yields.

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?

Explicitly says when to use it: 'before gated tools or when asked about remaining access.' That is a concrete trigger condition. It does not name alternatives or exclusions, which is acceptable here since no sibling overlaps in purpose.

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

All Poly-Glot AI Workspace 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.