agentView

Search Store Templates

search_store_templates

Read-onlyIdempotent

Searches the agentView template store for ready-made display designs ('Zahnarzt-Wartezimmer', 'Bistro', 'reception', ...). Use when the user wants a polished pre-built design instead of generated HTML; results render as a gallery widget. Filter by category, suite and language; paginate with limit/offset. Follow up with get_store_template_details. No authentication required.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of templates to return. Defaults to 10.
`query`	No	Free-text search over template title, description and tags. Examples: 'Zahnarzt', 'italienisches Bistro', 'conference room'.
`suite`	No	Optional design-family suite slug (e.g. 'bistro-warm', 'sushi-minimal').
`offset`	No	Offset into the filtered result set for pagination. Defaults to 0.
`category`	No	Optional category slug to restrict the search (English kebab-case, e.g. 'gastronomie', 'waiting-room').
`language`	No	Preferred content language. Defaults to 'en'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`total`	No
`offset`	No
`language`	No
`templates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedJun 2, 2026
- changedOutput schema / properties / language / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / limit / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / offset / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / category / properties / slug / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / category / properties / title / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / category / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / description / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / designStyle / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / detailPath / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / featured / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / placement / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / previewImageUrl / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / previewPath / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / publishedAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / slug / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / suite / properties / slug / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / suite / properties / title / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / suite / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / tags / items / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / tags / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / theme / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / properties / title / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / templates / items / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / templates / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```
- changedOutput schema / properties / total / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

Changed22 schema fields changedMay 23, 2026

removedInput schema / properties / category / default
```
Removed value: -null
```

changedInput schema / properties / category / description

Previous value: -"Optional category slug to restrict the search (English kebab-case, e.g. 'gastronomie', 'waiting-room', 'reception'). Use list_store_categories to discover available slugs."New value: +"Optional category slug to restrict the search (English kebab-case, e.g. 'gastronomie', 'waiting-room')."

changedInput schema / properties / category / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

removedInput schema / properties / language / default
```
Removed value: -null
```

changedInput schema / properties / language / description

Previous value: -"Preferred content language for title and description. 'de' or 'en'. Defaults to 'en' when omitted."New value: +"Preferred content language. Defaults to 'en'."

addedInput schema / properties / language / enum
```
Added value: +[
+  "de",
+  "en"
+]
```

changedInput schema / properties / language / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

removedInput schema / properties / limit / default
```
Removed value: -null
```

changedInput schema / properties / limit / description

Previous value: -"Maximum number of templates to return, 1-50. Defaults to 10."New value: +"Maximum number of templates to return. Defaults to 10."

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"

removedInput schema / properties / offset / default
```
Removed value: -null
```
addedInput schema / properties / offset / minimum
```
Added value: +0
```

changedInput schema / properties / offset / type

Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"

removedInput schema / properties / query / default
```
Removed value: -null
```

changedInput schema / properties / query / description

Previous value: -"Free-text search over template title, description and tags. Examples: 'Zahnarzt', 'italienisches Bistro', 'conference room'. Omit to list everything (combine with category/suite filters)."New value: +"Free-text search over template title, description and tags. Examples: 'Zahnarzt', 'italienisches Bistro', 'conference room'."

changedInput schema / properties / query / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

removedInput schema / properties / suite / default
```
Removed value: -null
```

changedInput schema / properties / suite / description

Previous value: -"Optional suite slug to restrict the search to one design family (e.g. 'bistro-warm', 'sushi-minimal', 'praxis-calm')."New value: +"Optional design-family suite slug (e.g. 'bistro-warm', 'sushi-minimal')."

changedInput schema / properties / suite / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "language": {
+      "type": "string"
+    },
+    "limit": {
+      "type": "integer"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "templates": {
+      "items": {
+        "properties": {
+          "category": {
+            "properties": {
+              "slug": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "description": {
+            "type": "string"
+          },
+          "designStyle": {
+            "type": "string"
+          },
+          "detailPath": {
+            "type": "string"
+          },
+          "featured": {
+            "type": "boolean"
+          },
+          "placement": {
+            "type": "string"
+          },
+          "previewImageUrl": {
+            "type": "string"
+          },
+          "previewPath": {
+            "type": "string"
+          },
+          "publishedAt": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "suite": {
+            "properties": {
+              "slug": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "theme": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedMay 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds value by noting 'No authentication required' and 'results render as a gallery widget', which are behavioral details beyond what annotations provide. No contradictions.

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?

The description is three sentences, front-loading the core purpose. Each sentence serves a clear function: stating the action and examples (first sentence), usage context (second sentence), and filtering options with follow-up (third sentence). No redundant or unnecessary words.

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

Completeness4/5

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

Given the tool has 6 parameters, all schemas are complete, and there is an output schema (mentioned as gallery widget). The description provides enough context for an agent to decide when to use this tool and how to construct the search, including the follow-up step. The absence of return value details is compensated by the output schema reference.

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 description coverage is 100%, so the schema already documents all 6 parameters. The description adds practical examples for 'query' (e.g., 'Zahnarzt', 'italienisches Bistro') and clarifies 'suite' and 'category' as optional filters, enhancing the semantic understanding of how to use the parameters.

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 uses a specific verb ('Searches') and resource ('agentView template store for ready-made display designs'), with concrete examples like 'Zahnarzt-Wartezimmer'. It clearly distinguishes from siblings such as list_store_categories and get_store_template_details by noting the follow-up action and the gallery widget rendering.

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?

The description explicitly states when to use this tool: 'when the user wants a polished pre-built design instead of generated HTML'. It also explains how to filter and paginate, and recommends following up with get_store_template_details. While it doesn't explicitly exclude alternatives, the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agentView 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.

Resources

Need Help?