Aurinia XO MCP

get_offers

Read-only

Reports the promotion Aurinia XO (Kamianets-Podilskyi) is advertising publicly at this moment: the text of the active site banner, its promo code, the discount percent, and any condition attached to that code — notably requires_full_buyout, a code that applies only when the stay takes every bed in the hostel, with beds_required giving that bed count. The promo_code returned is the one to pass to get_availability or book. Read-only, no authorization. offers is an empty array when nothing is being advertised, which is the normal state between campaigns. Optional locale (ua, en, de, it, fr, pl, bg; default en) picks the banner language, falling back to the Ukrainian source where a translation is missing. Only the advertised banner is reported; other discount codes present in the system stay unlisted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_offers"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No	Banner language. Default en.

Output Schema

Name	Required	Description	Default
`locale`	No
`offers`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real value: no authorization required, empty offers array is the normal between-campaign state, and locale falls back to the Ukrainian source when a translation is missing. The conditional semantics of requires_full_buyout and beds_required are also explained. Only rate limits or caching behavior are absent.

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?

Front-loaded with the core purpose and the returned fields, with usage routing and empty-state semantics after. It is a dense single paragraph; the embedded gloss on requires_full_buyout is worth its length, but the sentence could be split for readability.

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?

An output schema exists, yet the description still names the key returned fields and their conditional meaning, plus the empty-array normal state. For a one-optional-parameter read tool, nothing an agent needs in order to call it or interpret the result is missing.

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% and the enum is documented in the schema, so the baseline is 3. The description still adds meaning by naming the default (en) and disclosing the translation-fallback behavior to Ukrainian, which the schema does not state.

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 ("Reports the promotion Aurinia XO ... is advertising publicly at this moment") and enumerates exactly what is returned: banner text, promo code, discount percent, condition. It is clearly distinct from siblings like get_availability and book, which it explicitly hands off to.

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?

Tells the agent that the returned promo_code is the value to pass to get_availability or book, which gives a concrete downstream workflow. It also scopes the tool ("Only the advertised banner is reported; other discount codes ... stay unlisted"), though it never states an explicit when-not-to-call condition beyond that.

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

All Aurinia XO MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?