Poly-Glot AI Workspace

Open a Poly-Glot template

get_template

Read-only

Retrieve a named template's fields and entitled prompt body. Use search_templates first to find the exact name; inaccessible templates return a paywall view without Pro fields or prompt content after the trial. Returns template, entitlement and localization data. Reading a template alone neither starts the trial nor consumes a send.

Input Schema

Name	Required	Description	Default
`name`	Yes	Required template name returned by search_templates.
`uiLanguage`	No	Language code for localized template fields; defaults to EN.	EN

Output Schema

Name	Required	Description	Default
`view`	Yes
`message`	No
`template`	Yes
`entitlement`	Yes
`localization`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 8, 2026
- addedInput schema / properties / name / description
```
Added value: +"Required template name returned by search_templates."
```
- addedInput schema / properties / uiLanguage / description
```
Added value: +"Language code for localized template fields; 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

A4.7/5.0

Behavior4/5

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

Goes beyond the readOnly/destructive annotations by disclosing what an inaccessible template actually returns (paywall view without Pro fields or prompt content after trial) and that reading does not start the trial or consume a send. This is meaningful side-effect and failure-mode context, though it does not cover rate limits or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core action, then routing, then failure semantics, then the caveat about trial/send consumption. Every sentence carries distinct information with no filler.

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, the description needn't enumerate return values, yet it still summarizes them (template, entitlement, localization) and covers the critical entitlement/paywall edge case. Nothing needed to invoke this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description meaningfully constrains the 'name' parameter by stating it must be the exact name returned by search_templates, and it hints that localization affects returned fields ('localization data'), which ties the uiLanguage parameter to its effect.

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 ('Retrieve a named template's fields and entitled prompt body') and immediately distinguishes itself from search_templates, which only locates names. An agent can tell this is the fetch-by-name counterpart to search.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use search_templates first to find the exact name.' It also names the failure condition (inaccessible templates return a paywall view) and clarifies the non-side-effect nature of calling it, so the agent knows when this is safe and when it will get degraded results.

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.