Skip to main content
Glama

Get price range

get_pricing
Read-onlyIdempotent

Get the price range for a WEE WiLDS unit.

Returns a static min/max GBP range. Dynamic per-night quotes are not yet
available — for an exact quote, use send_inquiry.

Args:
    unit: One of "muckle-meadow-pod", "cosie-coorie-pod", "bb".
    check_in: Ignored for now (kept for forward-compat with dynamic pricing).
    check_out: Ignored for now (kept for forward-compat with dynamic pricing).

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": {
      "unit": "<unit>"
    },
    "name": "get_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesWhich WEE WiLDS unit: "muckle-meadow-pod" (Muckle Meadow Glamping Pod), "cosie-coorie-pod" (Cosy Coorie Pod) or "bb" (the B&B, all 4 rooms).
check_inNoOptional arrival date, YYYY-MM-DD. Not used yet: the range is the same for any dates.
check_outNoOptional departure date, YYYY-MM-DD. Not used yet: the range is the same for any dates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / check_in / description
      Added value: +"Optional arrival date, YYYY-MM-DD. Not used yet: the range is the same for any dates."
    • addedInput schema / properties / check_out / description
      Added value: +"Optional departure date, YYYY-MM-DD. Not used yet: the range is the same for any dates."
    • addedInput schema / properties / unit / description
      Added value: +"Which WEE WiLDS unit: \"muckle-meadow-pod\" (Muckle Meadow Glamping Pod), \"cosie-coorie-pod\" (Cosy Coorie Pod) or \"bb\" (the B&B, all 4 rooms)."
    • addedInput schema / properties / unit / enum
      Added value: +[
      +  "muckle-meadow-pod",
      +  "cosie-coorie-pod",
      +  "bb"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive/closed-world behavior, so the safety profile needs no restating. The description adds genuinely useful behavior beyond that: the range is static, date arguments are currently ignored, and the parameters are retained only for forward compatibility — exactly the kind of surprise an agent needs warned about.

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?

Front-loaded with purpose and return shape, then the alternative, then a compact Args block. No filler sentences; the repeated 'Ignored for now' phrasing is the only mild redundancy and it serves a real warning function.

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?

With no output schema, the description correctly compensates by naming the return value (static min/max GBP range). For a 3-parameter read-only tool this is close to complete; only minor detail such as whether the range varies by unit is left implicit.

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%, including the enum breakdown of each unit and the note that dates are unused, so the schema already carries full parameter meaning. The description's Args block repeats the same enum values and the same 'ignored for now' note rather than adding syntax, defaults, or edge cases on top.

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?

States a specific verb and resource ('Get the price range for a WEE WiLDS unit') plus the exact shape of what comes back ('static min/max GBP range'), and explicitly separates itself from send_inquiry, which returns exact quotes. An agent can distinguish this from the quote-producing sibling without opening either schema.

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?

Gives an explicit when-not plus the alternative: dynamic per-night pricing is unavailable, so 'for an exact quote, use send_inquiry.' It does not explicitly position itself against get_availability or get_unit_details, but the guidance about which tool to pick for pricing is clear.

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