Skip to main content
Glama

Back to the usual price

reset_nightly_price
Destructive

Removes the own price of nights in a range, so they go back to the season or base price. For one unit or (without unit_id) every unit. 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>"
    },
    "name": "reset_nightly_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD, inclusive. Default: same as from.
fromYesYYYY-MM-DD
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idNoLeave out for every unit.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is signaled structurally; the description earns credit by explaining exactly what is destroyed (the per-night override) and what results (fallback to season/base price), including that a bare call without unit_id touches every unit. It does not address reversibility or how to restore prices, but the annotation carries the destructive framing.

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?

Three short sentences, front-loaded with the core action and effect, then scoping rules, then the venue/address requirement. No redundant restatement of the title or schema.

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, single-venue mutation with a fully documented 5-parameter schema and no output schema, the description covers effect, scope, and the address/access-key requirement. Minor gaps remain around confirming what the response contains and whether the reset can be undone by re-setting.

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 100%, so the baseline is 3, but the description adds real meaning: the relationship that omitting unit_id applies the reset to every unit and that a single-night reset needs only 'from' because 'to' defaults to it. Those are usage-level semantics beyond the field-by-field schema text.

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 ('Removes the own price of nights in a range') and explains the resulting state ('back to the season or base price'), which distinguishes it from the additive behavior of a set operation. It does not name set_nightly_price or list_nightly_prices explicitly, so sibling routing still relies on inference.

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 scope guidance: one unit via unit_id, every unit when omitted, and 'For one night, send only from.' That covers the main usage decision points. It never states when to prefer this over set_nightly_price (e.g., to clear rather than overwrite) or any preconditions on the range, so it stops short of full when/when-not guidance.

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