Skip to main content
Glama

Sauna & cold plunge buying guide

get_equipment_pricing
Read-only

What it costs to buy a sauna, a cold plunge or both, for home or for a commercial studio: researched price ranges, the costs buyers forget (electrical, site work, delivery), the mistakes that cost the most, example products with live prices, and a free quote option. Use for any question about buying or pricing sauna or cold plunge equipment.

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": {
      "interest": "<interest>",
      "use": "<use>"
    },
    "name": "get_equipment_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
useYeshome, or commercial (studio, gym, spa, team facility)
interestYessauna, cold_plunge or both

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description complements them by disclosing the shape of the returned content (researched ranges, forgotten costs like electrical and site work, example products with prices, a quote path). The only soft tension is "live prices" plus a "free quote option" against openWorldHint=false, which implies no external fetch — worth a caveat but not a flat contradiction, since the content could be curated.

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?

One front-loaded sentence built around the core question ("what it costs"), followed by a single usage directive. The mid-sentence catalogue of covered topics is long but every item is a distinct content promise rather than filler, so it stays efficient with only slight density cost.

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?

For a two-enum-parameter informational lookup with no output schema, the description does the necessary work: it names the subject, the two axes, the content delivered, and the trigger condition. What is missing is the routing contract against its two siblings, which matters because one of them is a quote-request tool that this description partly advertises.

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% with enums on both parameters, so the baseline is 3. The description adds modest but real meaning by spelling out the commercial case as "studio" and framing the two parameters as the home-vs-commercial and sauna-vs-cold-plunge axes of the guide, which helps an agent see why both are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete subject (cost of buying sauna / cold plunge equipment) and its scope (home vs. commercial studio), and enumerates the content it covers: price ranges, hidden costs, common mistakes, example products, and a quote option. It is clear what the tool is for, but it never names the sibling tools it overlaps with (request_equipment_quote, find_studios), so differentiation is left to inference.

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?

"Use for any question about buying or pricing sauna or cold plunge equipment" is an explicit trigger condition covering a well-bounded question class. There is no when-not guidance, though — notably no statement about when an agent should call request_equipment_quote instead of this guide, even though the description advertises a "free quote option" that overlaps with that sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources