Poly-Glot AI Workspace

Build a Poly-Glot prompt

build_prompt

Fill a named Poly-Glot template with field values and requested input/output languages, producing a finished prompt. Use get_template to inspect needed fields first. This is a subscription-gated Send. Eligible users must authorize a three-day Pro introductory trial through Apple's native subscription purchase flow, or have an active verified Pro subscription or an unexpired legacy trial. There is no continuing free-Send allowance. This tool cannot start an Apple subscription or trial and does not directly query external AI providers.

Input Schema

Name	Required	Description	Default
`name`	Yes	Required accessible template name; use search_templates or get_template to find it.
`values`	No	Map of template placeholder names to strings, numbers or booleans, e.g. {topic: onboarding}.
`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
`name`	No
`view`	Yes
`prompt`	No
`message`	No
`template`	No
`entitlement`	Yes
`localization`	Yes
`inputLanguage`	No
`missingFields`	No
`outputLanguage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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: +"Required accessible template name; use search_templates or get_template to find it."

addedInput schema / properties / outputLanguage / description

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

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: +"Map of template placeholder names to strings, numbers or booleans, e.g. {topic: onboarding}."

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

Behavior5/5

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

Goes well beyond the annotations, which only declare readOnlyHint=false, openWorldHint=false, destructiveHint=false. The description discloses subscription gating, the three-day Pro trial path, absence of a continuing free-Send allowance, the fact it cannot start a subscription, and that it does not query external AI providers — all material to whether the call can succeed.

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-loads what the tool does, then the prerequisite, then the gating rules — a sensible order with no filler sentences. The subscription paragraph is dense and longer than typical, though each clause carries actionable constraint information.

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?

With an output schema present, return values need not be explained, and the description covers the remaining burdens: prerequisites, eligibility, and explicit non-capabilities. An agent has what it needs to decide whether to call this or a sibling.

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 every parameter (including the values map and the three language fields) is already documented in the schema. The description only gestures at "field values and requested input/output languages" without adding format or edge-case meaning, so the 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 and resource: fill a named Poly-Glot template with field values and language settings to produce a finished prompt. It also implicitly separates itself from get_template/search_templates by framing those as inspection tools used beforehand.

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?

Gives a concrete prerequisite ("Use get_template to inspect needed fields first") and detailed eligibility conditions for use. It stops short of naming alternative tools for cases where the agent is not eligible or doesn't want a template-based prompt, so it is clear context rather than full when/when-not routing.

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.