Skip to main content
Glama

Dynamic Pricing & Overbooking

Server Details

Set prices, protection levels and overbooking limits from demand and remaining capacity.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
Saify-Technologies/saifs-ai-mcps-docs
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation4/5

The two tools have mostly distinct purposes: one runs the analysis inline, the other returns a Python script for large datasets or sandbox use. The boundary is explicitly defined by data-size thresholds, though both ultimately perform the same engine, which introduces slight conceptual overlap.

Naming Consistency3/5

Both names use snake_case and share the revenue_optimizer prefix. However, the first is a bare noun while the second appends a verb phrase (_get_engine), so the convention is mixed rather than a predictable verb_noun pattern.

Tool Count3/5

Only two tools exist for a broad yield-management and overbooking domain. The first tool is extremely dense and the second is essentially an escape hatch, making the surface feel thin despite the functionality packed into one tool.

Completeness4/5

The surface covers core forecasting, pricing, elasticity, protection levels, and overbooking recommendations with a large-data fallback. It is not a CRUD lifecycle, but the analytical domain is well covered; minor gaps include no separate lightweight tools for isolated pricing or overbooking queries.

Available Tools

2 tools
revenue_optimizerDynamic Pricing, Booking Pace, Protection Levels & OverbookingA
Read-only
Inspect

Yield management for perishable capacity (hotel rooms, seats, tickets, rentals, slots, covers). From products (capacity, sold, days to the date, price, floor/ceiling) and optional bookings (stay/event date, lead time or booking date, status, class, price, segment), price history (date, price, units), fare classes (fare, demand still to come) and show history it returns: booking pace vs comparable past dates and an additive-pickup forecast with range; the price now maximising expected contribution within a band (demand from pickup x price response); price elasticity by log-log regression with confidence interval, refusing flat-price or demand-driven histories, pooled across products; Littlewood / EMSR-a / EMSR-b protection levels and booking limits with the exact optimal levels and expected revenue vs first-come-first-served; overbooking limit (binomial shows) with the chance of turning anyone away, show rates by segment with Beta-Binomial shrinkage, never for critical clinic types. Recommendations only. Decision cards first. Up to 500 products / 20,000 bookings; larger: revenue_optimizer_get_engine.

Inputs: as_of, bookings, capacity, currency, +16 more. Returns: alerts, status, message, summary, +8 more

revenue_optimizer_get_engineRevenue Optimizer — Get Engine Script (large histories)A
Read-only
Inspect

For more than 500 products, 20,000 bookings or 5,000 price-history rows, or any such file already in your code sandbox. Returns a complete numpy-only Python script with the same engine as revenue_optimizer; it reads products, fare classes, price history, bookings and show history, prints the decision cards and one line per product, and writes everything to revenue_plan.json. No booking data reaches this server on this path.

Inputs: params, bookings_path, products_path, fare_classes_path, +2 more. Returns: notes, paths, script, language, +7 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.