search_templatesFind Poly-Glot prompt templates. Results include whether each template is currently locked for this account. Searching does not start the trial or consume a send.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | ||
| plan | No | ||
| limit | No | ||
| query | No | ||
| uiLanguage | No | EN |
| Name | Required | Description | Default |
|---|---|---|---|
| view | Yes | ||
| query | Yes | ||
| results | Yes | ||
| entitlement | Yes | ||
| localization | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / entitlement / properties / compareLockedAdded value: +{
+ "type": "boolean"
+}Output schema / properties / entitlement / properties / dailyFreeLimitAdded value: +{
+ "type": [
+ "number",
+ "null"
+ ]
+}Output schema / properties / entitlement / properties / nextResetAtAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Despite readOnlyHint and destructiveHint annotations, the description adds value by clarifying that searching does not start the trial or consume a send, and that results include lock status. This goes beyond the annotations and provides useful side-effect information without contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, with three short sentences that each add distinct information: purpose, result contents, and side-effect safety. It is front-loaded with the primary action and contains no filler or redundant phrasing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the output schema covers return structure and annotations cover safety, the description leaves parameter semantics unaddressed and offers no guidance on selecting this tool over get_template. This is a meaningful gap for a search tool with 5 optional parameters, though the tool is simple enough to remain minimally viable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description provides no explanation of the parameters (goal, plan, limit, query, uiLanguage). The description fails to compensate for the lack of schema descriptions, leaving agents to guess parameter meanings from names alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states a specific action ('Find Poly-Glot prompt templates') and resource. It distinguishes from sibling get_template by indicating search behavior and including lock status in results. This provides enough differentiation for an agent to select this tool over alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the tool name and description, but there is no explicit guidance on when to use this tool versus alternatives like get_template. The note about not starting a trial or consuming a send adds some usage context, but no exclusions or alternative comparisons are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.