Poly-Glot AI Workspace

Search Poly-Glot templates

search_templates

Read-only

Search Poly-Glot's template catalog by keywords and goal, optionally filtered to free or Pro results. Use before get_template or build_prompt when the exact name is unknown. Expired accounts see locked Pro template cards. Selecting one returns a paywall, not Pro fields or prompt text. Searching is read-only and does not trigger a send or trial.

Input Schema

Name	Required	Description	Default
`goal`	No	Optional intended outcome, e.g. write a help article.
`plan`	No	Filter catalog by free or Pro tier; filtering does not grant access.
`limit`	No	Maximum matches to return (1 to 24), default 12.
`query`	No	Search phrase or topic; blank lists available templates.
`uiLanguage`	No	Language code for localized 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.

Changed7 schema fields changedOct 8, 2026

addedInput schema / properties / goal / description

Added value: +"Optional intended outcome, e.g. write a help article."

addedInput schema / properties / limit / description

Added value: +"Maximum matches to return (1 to 24), default 12."

addedInput schema / properties / plan / description

Added value: +"Filter catalog by free or Pro tier; filtering does not grant access."

addedInput schema / properties / query / description

Added value: +"Search phrase or topic; blank lists available templates."

addedInput schema / properties / uiLanguage / description

Added value: +"Language code for localized 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

A4.7/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations by disclosing account-tier behavior: expired accounts see locked Pro cards, and selecting one yields a paywall rather than Pro fields or prompt text. It also confirms searching triggers no send or trial, which is real behavioral context an agent needs to interpret results.

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 tight sentences, front-loaded with the operation and its scope, then routing guidance, then the paywall edge case, then the side-effect reassurance. Each sentence contributes distinct information and there is 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?

An output schema exists, so return structure need not be restated; the description instead covers the two things that would otherwise be missing — when to reach for it versus get_template/build_prompt, and how tier-locked results behave. Nothing needed to call it correctly is absent.

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, goal, plan, limit and uiLanguage are already fully documented, and the description adds no syntax or format detail beyond echoing keywords/goal/free-Pro. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (Search) and resource (Poly-Glot's template catalog) plus the axis of search (keywords and goal) and an optional filter (free/Pro). It is immediately distinguishable from siblings like get_template and build_prompt, which the description explicitly positions itself before.

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?

Gives an explicit precondition — 'Use before get_template or build_prompt when the exact name is unknown' — naming both alternatives and the condition that selects this tool over them. Nothing about routing is left 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.