store

Search Policies and FAQs

search_policies_and_faqs

Read-onlyIdempotent

Search Bolot Studio FAQs and store policies. Covers product questions, sizing, finishes, shipping, returns, and ordering.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_policies_and_faqs"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search query (e.g. 'returns', 'shipping to Germany', 'matte vs glossy', 'desk stand')
`locale`	No	Locale code for localized policy URLs (e.g. 'en', 'pl', 'de')
`country`	No	ISO 3166-1 alpha-2 or alpha-3 country code for locale-aware policy URLs (e.g. 'PL', 'DE', 'GB', 'DEU', 'GBR')

Output Schema

Name	Required	Description	Default
`faqs`	No
`error`	No
`locale`	No
`message`	No
`policy_links`	No
`total_matches`	No
`locale_fallback`	No
`_response_budget`	No
`returned_matches`	No
`shipping_by_country`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 14, 2026

addedOutput schema / properties / _response_budget

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "dropped": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "limit_bytes": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "dropped",
+    "limit_bytes",
+    "note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 4, 2026

changedOutput schema / properties / faqs / items / properties / source / enum

Previous value: -[
-  "faq_page",
-  "product_faq"
-]New value: +[
+  "faq_page",
+  "product_faq",
+  "guarantee"
+]

Changed6 schema fields changedAug 3, 2026
- addedOutput schema / properties / faqs / items / properties / locale
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / faqs / items / properties / source
```
Added value: +{
+  "enum": [
+    "faq_page",
+    "product_faq"
+  ],
+  "type": "string"
+}
```
- changedOutput schema / properties / faqs / items / required
```
Previous value: -[
-  "product",
-  "question",
-  "answer"
-]New value: +[
+  "question",
+  "answer"
+]
```
- addedOutput schema / properties / locale
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / locale_fallback
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / returned_matches
```
Added value: +{
+  "type": "number"
+}
```
First observedJul 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so the safety profile is clear. The description adds no extra behavioral context like pagination, authentication, or locale-specific behavior, but it does not contradict annotations.

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 a single, front-loaded sentence that directly states purpose and key coverage topics. No filler words or redundant details.

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?

Given the low complexity of a search tool, the presence of an output schema, and strong annotations, the description sufficiently captures the tool's purpose and scope. It clearly defines what is searched and which topics are covered, with no missing critical context.

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%, with each parameter (query, locale, country) already described with examples. The description does not add additional parameter semantics beyond the schema's own descriptions.

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 tool searches Bolot Studio FAQs and store policies, with a specific verb and resource. It also lists coverage areas (product questions, sizing, finishes, shipping, returns, ordering) that distinguish it from sibling product search tools like search_products.

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 implies usage for policy/FAQ questions via the coverage list, but it does not explicitly say when to use this tool instead of alternatives such as search_products or get_store_info. No exclusions or alternative recommendations are provided.

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

All store 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?