Skip to main content
Glama

rakentaja-outlet

by fi.rakentajaoutlet

search_shop_policies_and_faqs

Read-onlyIdempotent

Search Rakentaja Outlet shop policies, FAQ, and store info.

Searches across 8 pages: About Us (tietoa-meista), FAQ (usein-kysyttya), Delivery terms (toimitusehdot), Privacy Policy (tietosuoja), Terms of Use (kayttoehdot), Return Form (peruutuslomake), Payment Methods (maksutavat), AI Agent Guide (ai).

Use this tool when the user asks about:

  • Delivery times and costs ("toimitusaika", "toimituskulu")

  • Returns and refunds ("palautus", "peruutus", "hyvitys")

  • Payment methods ("maksutavat", "lasku")

  • Privacy or GDPR ("tietosuoja", "GDPR")

  • Terms of use ("käyttöehdot")

  • Company information ("Sanere Oy", "yhteystiedot", "Y-tunnus")

  • Any general question about buying from the store

Args: query: Free-text search term (Finnish). Case-insensitive. Leave empty to get an overview of all policy pages. limit: Maximum sections to return (1-10, default 5). Each section is a paragraph or Q&A pair; longer content is truncated.

Returns: JSON with: - sections: list of matching sections, each with: - page_slug: e.g. "usein-kysyttya" - page_title: e.g. "Usein kysyttyä" - page_url: full URL to the page - heading: section heading if any - text: matching text content (may be truncated) - is_faq: True if this is a Q&A from the FAQ page - total_matches: total sections matched - query: echoed query - available_pages: list of all policy page slugs - disclaimer: legal reminder to check the full page

Notes: - Policies are the authoritative source; if unclear, direct the user to the page_url for the full text. - Some FAQ entries are marked with FAQPage schema.org markup — these show up as Google rich results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax sections to return (1-10)
queryNoFree-text search term (Finnish)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesEchoed query
sectionsYesMatching sections (limited by `limit`)
disclaimerYes
total_matchesYesTotal sections matched (may be > len(sections) if limited)
available_pagesYesAll 8 policy page slugs

TDQS

A4.5/5.0
Behavior4/5

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

Description adds context beyond annotations: lists exact pages searched, mentions resulting sections, FAQ flag, disclaimer, and schema.org markup. Annotations already show it is read-only and idempotent.

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

Conciseness4/5

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

Well-structured with clear sections (purpose, usage, args, returns, notes). Slightly lengthy but all sentences are informative and not redundant.

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 tool complexity (searching multiple pages, 2 params, output schema exists), description fully covers what the tool does, how to use it, and what to expect in return. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds meaningful details beyond schema: query is Finnish case-insensitive, empty for overview; limit defines sections as paragraphs or Q&A pairs with truncation. Schema coverage is 100% but description enriches understanding.

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?

Description clearly states it searches shop policies, FAQ, and store info across 8 specific pages, with a verb ('search') and specific resource. Distinct from sibling tools like search_catalog or get_product_details.

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?

Explicitly lists when to use with example queries (delivery, returns, payment, etc.). Does not explicitly state when not to use, but context implies for policy-related queries only.

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

All rakentaja-outlet toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: cart link generation, product details, catalog search, and policy/FAQ search. No overlap or ambiguity.

Naming Consistency5/5

All tools use a consistent verb_noun pattern in snake_case: create_cart_link, get_product_details, search_catalog, search_shop_policies_and_faqs.

Tool Count4/5

With 4 tools, the set is well-scoped for a store assistant. It covers core shopping flows without being bloated. A category listing tool could be a minor addition.

Completeness4/5

Covers product search, details, cart creation, and policies. Missing user account or order management, but these are reasonable omissions for the assistant role.

Resources