Skip to main content
Glama

Remove a seasonal price

remove_season
Destructive

Deletes a seasonal price. Nights in it go back to the base price. Existing bookings keep their agreed total. 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>",
      "season_id": "<season_id>"
    },
    "name": "remove_season"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
season_idYesId of the seasonal price.
access_keyYesThe venue’s access key.

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 flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: affected nights revert to the base price and existing bookings retain their agreed total, which tells the agent the blast radius is limited. It stops short of stating whether the deletion is reversible or requires confirmation, keeping it at 4.

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?

Four short sentences, front-loaded with the action and its consequence, with no filler. The closing sentence about operating on one venue with an address and access key is mildly redundant with the schema but still frames the scope.

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 destructive, non-idempotent mutation with no output schema, the definition covers the essential unknowns — what gets deleted, what happens to affected nights, and that existing bookings are unaffected. It could additionally state failure behavior for an unknown season_id to be fully complete.

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%, so all three parameters (address, season_id, access_key) are already documented. The description only restates that the address and access key identify the single venue, adding minimal meaning beyond the schema; the baseline 3 applies.

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 opens with a specific verb+resource: "Deletes a seasonal price," which is clearly separable from siblings like reset_nightly_price or remove_weekly_class by resource noun. It does not explicitly name an alternative tool, but the resource is unambiguous enough that an agent can select it without opening the schema.

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?

Usage context is implied rather than stated: the agent learns the tool acts on a single venue and what the pricing consequence is, but there is no explicit "use this when / not when" guidance or mention of a prerequisite such as the season existing. Adequate but leaves selection reasoning to inference.

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