Poly-Glot AI Workspace

Build a Poly-Glot prompt

build_prompt

Fill and Send an entitled Poly-Glot template. This is a Send action: it starts the 3-day free trial on first use if the user has not sent before. Pro templates require an active trial or Pro subscription.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	Yes
`values`	No
`uiLanguage`	No	EN
`inputLanguage`	No	EN
`outputLanguage`	No	EN

Output Schema

TableJSON 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.

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

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds meaningful behavior: it starts a 3-day free trial on first use and notes that Pro templates require an active trial or subscription. This goes beyond the annotations and warns about side effects, which is valuable for an agent deciding whether to invoke the tool.

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?

The description is only two sentences and gets straight to the point, with the primary action front-loaded. It wastes no words, though the trial/subscription detail is somewhat tangential but still relevant. Overall it is efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 params, 1 required, nested objects, output schema present but not visible), the description covers the core action and a side effect but omits details like what the tool returns, what 'entitled' means, and any prerequisites (e.g., does the template already need to exist?). The presence of an output schema may cover return values, but the description itself is incomplete for a full picture.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden of explaining parameters. It mentions 'Fill' but does not map any of the five parameters (name, values, uiLanguage, inputLanguage, outputLanguage) to their purpose or format. The agent is left guessing what 'values' or the language parameters mean, and the description does not compensate for the lack of schema documentation.

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?

The description clearly states the action: 'Fill and Send an entitled Poly-Glot template.' It identifies a specific verb ('Fill and Send'), a specific resource ('entitled Poly-Glot template'), and distinguishes it from sibling tools like get_template (which retrieves a template) and localize_text/translate_text (which transform content). The purpose is unambiguous.

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

Usage Guidelines3/5

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

The description indicates this is a 'Send action' and mentions trial/subscription requirements, but it does not explicitly say when to use this tool versus alternatives, nor does it name siblings or provide conditions for when not to use it. The usage context is implied (send a template) but no exclusions or alternative routing are given.

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.