Poly-Glot AI Workspace

Prepare Poly-Glot Compare Mode

prepare_compare

Prepare the same canonical prompt for two to eight selected AI providers using a raw prompt or accessible template. Returns provider destinations, prompt and usage instructions without calling third-party models. This is a subscription-gated Send; Compare Mode requires a verified Apple subscription or an unexpired legacy trial. MCP cannot start an introductory offer. Use when a user explicitly wants side-by-side answers.

Input Schema

Name	Required	Description	Default
`name`	No	Optional accessible template name; supply this or a raw prompt.
`prompt`	No	Optional original prompt for each provider, maximum 30,000 characters; provide this or name.
`values`	No	Placeholder values used when preparing a named template.
`providers`	No	Two to eight provider IDs; defaults to ChatGPT and Claude and duplicates are removed.
`uiLanguage`	No	Interface language name or code, e.g. EN; independent of source and response languages.	EN
`inputLanguage`	No	Language name or code of input text, e.g. es; defaults to EN.	EN
`outputLanguage`	No	Requested output language name or code, e.g. fr; defaults to EN.	EN

Output Schema

Name	Required	Description	Default
`view`	Yes
`prompt`	No
`message`	No
`template`	No
`providers`	No
`entitlement`	Yes
`instructions`	No
`localization`	Yes
`sourceTemplate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 13, 2026

changedInput schema / properties / providers / description

Previous value: -"Two to nine provider IDs; defaults to ChatGPT and Claude and duplicates are removed."New value: +"Two to eight provider IDs; defaults to ChatGPT and Claude and duplicates are removed."

changedInput schema / properties / providers / items / enum

Previous value: -[
-  "chatgpt",
-  "claude",
-  "gemini",
-  "perplexity",
-  "grok",
-  "copilot",
-  "mistral",
-  "huggingchat",
-  "duckduckgo"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "gemini",
+  "perplexity",
+  "grok",
+  "mistral",
+  "huggingchat",
+  "duckduckgo"
+]

changedInput schema / properties / providers / maxItems
```
Previous value: -9New value: +8
```

Changed11 schema fields changedOct 8, 2026

addedInput schema / properties / inputLanguage / description

Added value: +"Language name or code of input text, e.g. es; defaults to EN."

addedInput schema / properties / name / description

Added value: +"Optional accessible template name; supply this or a raw prompt."

addedInput schema / properties / outputLanguage / description

Added value: +"Requested output language name or code, e.g. fr; defaults to EN."

addedInput schema / properties / prompt / description

Added value: +"Optional original prompt for each provider, maximum 30,000 characters; provide this or name."

addedInput schema / properties / providers / description

Added value: +"Two to nine provider IDs; defaults to ChatGPT and Claude and duplicates are removed."

changedInput schema / properties / providers / items / enum

Previous value: -[
-  "chatgpt",
-  "claude",
-  "gemini",
-  "perplexity",
-  "grok",
-  "copilot",
-  "mistral"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "gemini",
+  "perplexity",
+  "grok",
+  "copilot",
+  "mistral",
+  "huggingchat",
+  "duckduckgo"
+]

changedInput schema / properties / providers / maxItems
```
Previous value: -7New value: +9
```

addedInput schema / properties / uiLanguage / description

Added value: +"Interface language name or code, e.g. EN; independent of source and response languages."

addedInput schema / properties / values / description

Added value: +"Placeholder values used when preparing a named template."

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.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, so the description's clarification that this only prepares and returns destinations/instructions without invoking third-party models is genuinely valuable. It also discloses the auth requirement (verified Apple subscription or unexpired legacy trial) and the limitation that MCP cannot start an introductory offer — real context beyond structured fields.

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?

Front-loaded with the core action and return shape before moving to gating and usage. Slightly redundant: 'This is a subscription-gated Send' and 'Compare Mode requires a verified Apple subscription or an unexpired legacy trial' restate the same constraint in adjacent sentences.

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 an output schema present, return values need not be explained, and the description covers behavior, gating, and a usage trigger for a zero-required-parameter tool with nested objects. Only the sibling alternative (prepare_custom_compare) is unaddressed, which is a modest gap.

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 coverage is 100%, so all seven parameters (including the prompt/template either-or and the 2-8 provider bound) are already documented in the schema. The description reinforces the either-or input choice and the provider count but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (prepare), resource (canonical prompt for 2-8 providers), and inputs accepted (raw prompt or accessible template). It also draws a clear boundary by declaring it returns destinations/instructions 'without calling third-party models,' which separates it from run_custom_model-style siblings.

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?

'Use when a user explicitly wants side-by-side answers' gives a clear triggering condition, and the subscription gating spells out a prerequisite the agent must check beforehand. It does not name the nearest alternative (prepare_custom_compare) for when the user wants a custom rather than a canonical prompt, so routing is left partly to inference.

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.