Skip to main content
Glama

Add a seasonal price

add_season

A date range with a different price per night (high season, Easter…), for one unit or for all. Nights inside it use this price instead of the unit’s base price. A season for a specific unit wins over one for all units; a night’s own price wins over both. 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>",
      "to": "<to>",
      "price_per_night_eur": "<price_per_night_eur>"
    },
    "name": "add_season"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast night (inclusive), YYYY-MM-DD.
fromYesFirst night, YYYY-MM-DD.
nameNoOptional label, e.g. "August".
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idNoLeave out to apply to all units.
access_keyYesThe venue’s access key.
min_nightsNoOptional minimum stay for bookings that start in this season (2-60).
price_per_night_eurYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the safety profile is covered. The description adds meaningful context on top: it names the authentication requirement (venue address plus access key), the scope resolution logic between unit-specific and all-unit seasons, and how the price interacts with the base price — all behavior an agent could not derive from the hints. It stops short of saying what happens on overlap with an existing season or what the response returns.

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?

Three sentences, front-loaded with what the resource is, then the resolution rules, then the access requirement — each sentence carries distinct information. Slightly dense in the middle with combined clauses about precedence, but no padding or repetition.

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 an eight-parameter mutation tool with no output schema, the description covers the essentials: what is created, its scope, its precedence over base prices, and the credential needed to act on a venue. Remaining gaps — edge cases for overlapping seasons, error behavior, and what min_nights implies — are modest relative to what annotations and the well-covered schema already supply.

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 coverage is 88%, so nearly every parameter is already documented, and the description largely restates that the range applies to one unit or all. It contributes the pricing precedence that gives unit_id and the date range meaning in combination, but adds nothing about min_nights or the format of price_per_night_eur. Baseline 3 is appropriate given the schema does the heavy lifting.

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 defines the resource precisely — a date range carrying a different per-night price, applicable to one unit or all — which tells an agent exactly what gets created. It lacks an explicit verb phrase ('adds a season to the venue') and never names a contrasting sibling such as set_nightly_price or remove_season, so differentiation is inferred from the pricing-override explanation rather than stated.

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

Usage Guidelines3/5

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

It gives real usage context through the precedence chain: nights inside the range use this price, a unit-specific season beats an all-unit season, and a night's own price beats both. That tells an agent how the season behaves once created, but there is no guidance on when to reach for this tool versus set_nightly_price or reset_nightly_price, and no stated prerequisites or caveats for overlapping seasons.

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