Skip to main content
Glama

Calculate villa price

get_price_quote

Calculates the current Lodgify price. Adults, children and infants are counted separately. All guests currently have the same price. Maximum 10 guests in total.

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": {
      "arrival": "<arrival>",
      "departure": "<departure>",
      "adults": "<adults>"
    },
    "name": "get_price_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
addonsNoOptional comma-separated Lodgify add-on IDs.
adultsYes
arrivalYes
infantsNo
childrenNo
departureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / addons / description
      Previous value: -"Optional comma-separated Lodgify add-on IDs, for example 151664,154438. Leave empty for no extras."New value: +"Optional comma-separated Lodgify add-on IDs."
    • addedInput schema / properties / adults
      Added value: +{
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / arrival / description
      Removed value: -"Arrival date in YYYY-MM-DD format."
    • addedInput schema / properties / children
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • removedInput schema / properties / departure / description
      Removed value: -"Departure date in YYYY-MM-DD format."
    • removedInput schema / properties / guests
      Removed value: -{
      -  "description": "Number of guests, between 2 and 10.",
      -  "maximum": 10,
      -  "minimum": 2,
      -  "type": "integer"
      -}
    • addedInput schema / properties / infants
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "arrival",
      -  "departure",
      -  "guests"
      -]New value: +[
      +  "arrival",
      +  "departure",
      +  "adults"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses useful constraints—adults, children, and infants are counted separately, all guests currently have the same price, and the maximum is 10 guests total—but it does not state whether the operation is read-only, how currency/fees/taxes are handled, or whether the quote is binding.

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?

The description is front-loaded with the core purpose and uses three tight sentences without obvious filler. Each sentence adds a constraint or clarification, though the structure could be slightly sharper by grouping related guest rules.

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

Completeness2/5

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

This is a 6-parameter pricing tool with no annotations and no output schema, so the description should explain more about the quote behavior and return context. It omits currency, fee/tax treatment, add-on effects, date requirements, and what happens when the 10-guest cap is exceeded.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description must compensate, but it explains only the guest-count parameters. It does not clarify the meaning or constraints of arrival, departure, or how add-ons affect the calculated price, leaving several low-coverage parameters under-specified.

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 specific verb and resource: "Calculates the current Lodgify price," and the title identifies it as a villa price calculation. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as check_availability or list_extras.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives like check_availability or list_extras, nor are there exclusions or prerequisites. Usage is only implied by the tool name and the price-calculation sentence.

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