Skip to main content
Glama

Set the price of specific nights

set_nightly_price

Gives its own price per night to one night or a range (e.g. Christmas), for one unit or (without unit_id) for every unit. It wins over seasons and the base price. weekdays limits it to some days of the week, e.g. ["fri","sat"] for weekends in July. Existing bookings keep their agreed total. For one night, send only from. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "from": "<from>",
      "price_per_night_eur": "<price_per_night_eur>"
    },
    "name": "set_nightly_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast night (inclusive), YYYY-MM-DD. Default: same as from.
fromYesFirst night, YYYY-MM-DD.
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idNoLeave out to set it on every unit.
weekdaysNoOptional: only these nights of the week.
access_keyYesThe venue’s access key.
price_per_night_eurYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description adds genuinely useful behavior: the price overrides seasons and base price, existing bookings keep their agreed total, and omitting unit_id applies the price to every unit (a broad, hard-to-notice side effect). That bulk-application warning and the booking-safety guarantee are exactly the kind of context annotations cannot carry. It stops short of saying what the tool returns or what happens on overlapping ranges.

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 core action is front-loaded in the first clause, followed by precedence, then scoping constraints, which is a sensible order. It is dense but efficient; the trailing sentence 'Acts on one venue, given its address and access key' largely restates schema fields and is the weakest use of space.

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 7-parameter mutation with no output schema, the description covers scope, precedence, bulk-application, and booking safety — enough to call it correctly. Gaps remain on return behavior and on precedence between weekdays and an explicit from/to range, but these are secondary for correct invocation.

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 coverage is 86%, so the baseline is 3; the description earns a bump by explaining parameter interactions rather than just restating fields — the from/to default ('For one night, send only from') and the weekdays example ('["fri","sat"] for weekends in July') show how the three combine. It does not explain the format of price_per_night_eur or currency assumptions beyond the field name.

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 opens with a precise verb + resource + scope: setting a per-night price for a single night or a range, for one unit or all units. It disambiguates from the season/base-price mechanisms by stating 'It wins over seasons and the base price', so an agent can tell this apart from pricing done via add_season or listing defaults.

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?

It gives concrete selection conditions: 'For one night, send only from', 'without unit_id for every unit', and 'weekdays limits it to some days of the week'. Precedence over seasons and base price is stated, which tells the agent when this is the right tool rather than season configuration. What is missing is an explicit pointer to the counterpart tool (e.g. reset_nightly_price) for undoing a price override.

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