Skip to main content
Glama
negm17111995

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get hotel tax rules

getHotelTaxSchema
Read-onlyIdempotent

Retrieve a hotel's normalized tax and fee schema to see whether charges are included, percentage-based, or fixed, and how fixed amounts scale per adult or night.

Instructions

Overview

Returns the tax schema of a hotel as normalized static data, independent of the supply provider the rules were learned from. Each entry describes one tax or fee: whether it is already included in the room rate, whether it is a percentage of the rate or a fixed amount, and how fixed amounts scale (per adult and/or per night).

When to Use

  • Price transparency - Show guests which taxes and fees apply at a property

  • Amount-due-at-property estimates - Excluded taxes are typically collected at the hotel

  • Tax auditing - Compare supplier-declared taxes against the reference schema

Notes

  • Fixed amounts are expressed in USD

  • Percentage rates apply to the room rate (e.g. 13.5 means 13.5%)

  • The schema is learned by an offline pipeline; hotels without learned data return 404

  • When the direct (hotel-declared) source is enabled, taxes declared by the hotel in MAQAMI Cloud take precedence over learned rules and each entry carries source, chargeType, appliedPer, appliedOn, payAtProperty and validity dates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hotelIdYesUnique identifier of the hotel, in 'lp' format or numeric.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds materially beyond them: 404 for hotels without learned data, USD-denominated fixed amounts, percentage semantics, and the direct-source precedence rule along with the extra fields each entry then carries.

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?

Markdown sections are front-loaded with the overview and each bullet carries information, not filler. Slightly longer than strictly necessary for a single-parameter read tool, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: it explains that each entry states inclusion in the room rate, percentage vs fixed, fixed-amount scaling granularity, and source/validity fields. An agent knows what it will get and under what failure condition.

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 coverage is 100% and hotelId's 'lp format or numeric' description lives in the schema, so the description adds no parameter-level detail. Baseline 3 is appropriate when the schema does all the work.

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?

States a specific verb and resource ('Returns the tax schema of a hotel') and adds a distinguishing qualifier: normalized static data independent of the supply provider. No sibling tool covers hotel tax rules, so the purpose is unambiguous.

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?

The 'When to Use' section gives three concrete scenarios (price transparency, amount-due-at-property estimates, tax auditing) that clearly frame the tool's context. It stops short of naming an alternative tool or stating when not to use it, but the context is explicit.

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

Deploy Server

Other Tools