Poly-Glot AI Workspace

Open Poly-Glot AI Workspace

open_workspace

Read-only

Open the embedded Poly-Glot prompt workspace and template browser, optionally prefiltered by a query and translated via uiLanguage. Returns the unlocked template catalog only for verified subscribers or valid legacy trials, plus entitlement and localization. An unsubscribed account receives no catalog results. Browsing is read-only and cannot start an Apple subscription.

Input Schema

Name	Required	Description	Default
`query`	No	Optional keyword or goal for template search, e.g. resume. Maximum 200 characters.
`uiLanguage`	No	UI language name or code for template labels; defaults to EN.	EN

Output Schema

Name	Required	Description	Default
`view`	Yes
`query`	Yes
`results`	Yes
`entitlement`	Yes
`localization`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 8, 2026

addedInput schema / properties / query / description

Added value: +"Optional keyword or goal for template search, e.g. resume. Maximum 200 characters."

addedInput schema / properties / uiLanguage / description

Added value: +"UI language name or code for template labels; defaults to EN."

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint/openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond them: entitlement-gated catalog results, silent empty results for unsubscribed accounts, and that browsing cannot initiate an Apple subscription.

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?

Four short sentences, front-loaded with the action and followed by the entitlement rule and read-only caveat; nothing is wasted, though the mention of returned 'entitlement and localization' data is redundant given the output schema.

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 annotations and an output schema present, the description only needs to cover access rules and intent, and it does so: entitlement gating, empty results for unsubscribed users, and read-only scope. Nothing critical to a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so query and uiLanguage are already documented with defaults and max lengths. The description only restates their roles (prefilter by query, translate via uiLanguage) without adding format or interaction semantics, so baseline 3 applies.

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?

The description names a specific verb (Open) and resource (Poly-Glot prompt workspace and template browser), with the optional prefilter/translation behavior spelled out. It is clearly distinct from lookup siblings like get_template or search_templates, though it never names an alternative explicitly.

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?

It gives clear when/when-not context: the workspace yields the unlocked catalog only for verified subscribers or valid legacy trials, and an unsubscribed account receives no results. That is strong gating guidance, but it does not point to alternative tools (e.g., search_templates) for users who want catalog data another way.

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.