Skip to main content
Glama

Nights with their own price

list_nightly_prices
Read-onlyIdempotent

Every night that has its own price, joined into ranges with the same price. For one unit or all. Defaults to today and the next 365 days. Seasonal prices are not included. 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>"
    },
    "name": "list_nightly_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD, inclusive. Default: from + 365 days.
fromNoYYYY-MM-DD. Default: today.
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idNoLeave out for all units.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds real value beyond them: the date defaults, the seasonal-exclusion boundary, the single-venue scoping, and the fact that address plus access key are needed. It does not discuss volume or pagination for a 365-day default range.

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?

Five short sentences, front-loaded with what the tool returns, followed by scope and defaults. Every sentence carries information; the only minor cost is the slightly staccato rhythm of the fragments.

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?

No output schema exists, so the description must convey the return shape; 'joined into ranges with the same price' does that in outline, but the fields of a range (start/end/price) and the behavior when no prices are set are unaddressed. For a read tool returning a nontrivial aggregate, this is thin.

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. The description nonetheless explains the semantic unit of the result ('joined into ranges with the same price') and the one-unit-or-all dimension, clarifying what the returned data means rather than merely restating the parameters.

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?

States a specific resource and scope: nights that have their own price, aggregated into ranges of equal price. The 'seasonal prices are not included' exclusion sharpens the boundary. It stops short of naming the sibling mutators (set_nightly_price, reset_nightly_price), which would have made it a 5.

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 through defaults (today + 365 days), the unit scoping rule, and the seasonal exclusion, so an agent can tell what a bare call returns. There is no explicit when-to-use versus alternatives guidance, and the read/mutate relationship with set_nightly_price or reset_nightly_price is left for the agent to infer.

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