Skip to main content
Glama
mikki321

night-margin-mcp

by mikki321

Compare pricing strategies on net

compare_strategies

Compares two pricing strategies to the baseline on net after turnover costs. Simulates gap-night discount vs. dropping short stays with price uplift — revealing when gross-optimizing fill is a net loss.

Instructions

Simulates two pricing strategies and compares them to the baseline on net after turnover costs: A fills gap nights at a discount (default 40% off the property's ADR), B drops bookings below a minimum stay and raises the remaining prices (default min 3 nights, +10%). Shows gross, net, net/night, occupancy, turnovers, and leak per scenario — revealing when gross-optimizing fill is a net loss. Strategy A assumes every gap night sells at the discounted price — an upper bound, not a forecast. Read-only simulation — never changes any prices. from/to are optional — without them the window defaults to the last 30 + next 90 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoPeriod end (exclusive), YYYY-MM-DD (optional — defaults to last 30 + next 90 days)
fromNoPeriod start, YYYY-MM-DD (optional — defaults to last 30 + next 90 days)
min_stayNoStrategy B: minimum stay in nights — bookings shorter than this are dropped (default 3)
uplift_pctNoStrategy B: price uplift percentage for the remaining bookings (default 10)
discount_pctNoStrategy A: gap night price discount as a percentage of the property's ADR (default 40)
Behavior4/5

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

The description explicitly states it is a read-only simulation that never changes prices, explains assumptions (e.g., Strategy A is an upper bound), and lists the metrics shown. Since no annotations exist, the description carries the burden well.

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 description is efficiently written and front-loaded with the purpose, though it could be slightly more concise; it is not overly verbose.

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?

Given no output schema and 5 optional parameters, the description covers strategies, defaults, assumptions, and metrics. It could mention edge cases or error conditions but is reasonably complete.

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%, but the description adds context beyond the schema by explaining the strategies' logic and default behaviors, enriching the meaning of parameters like discount_pct and uplift_pct.

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 clearly states it simulates and compares two pricing strategies to baseline, specifying the actions of each strategy. It distinguishes itself from sibling tools like 'analyze_portfolio' or 'gap_night_check' by being a dedicated simulation/comparison tool.

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?

The description implies the tool is for comparing pricing strategies but does not explicitly state when to use it over alternatives, nor does it provide exclusions or when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikki321/night-margin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server