Skip to main content
Glama
Sign In

Sparkling Tracks Tours

by com.sparklingtracks
OverviewDiscussionsAdmin

get_affiliate_services

Read-onlyIdempotent

List the affiliate booking services available on sparklingtracks.com (flights, hotels, cars, activities, eSIMs). Each entry is a whitelabel widget hosted on a site page; direct API booking is not supported through this MCP. The AI should route the user to the returned URL to complete the search and booking. Service titles and descriptions are currently English-only regardless of language param.

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_affiliate_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional category filter. If omitted, all categories are returned.
currencyNoCurrency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused.
languageNoOutput language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / currency / description
      Previous value: -"Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Unsupported values fall back to EUR. Default: EUR."New value: +"Currency for the price_localized fields. Conversion is approximate, EUR-based; the binding price at booking is always EUR. Default: EUR. A value outside the list is refused."
    • changedInput schema / properties / language / description
      Previous value: -"Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en. zh is Simplified Chinese."New value: +"Output language for translatable fields (city names, country names, trip titles, descriptions). Default: en. zh is Simplified Chinese. A value outside the list is refused."
  2. Changed1 schema field changed
    • changedInput schema / properties / currency / enum
      Previous value: -[
-  "EUR",
-  "USD",
-  "INR",
-  "CNY",
-  "GBP"
-]New value: +[
+  "EUR",
+  "USD",
+  "INR",
+  "CNY",
+  "GBP",
+  "CHF"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en."New value: +"Output language for translatable fields (city names, country names, trip titles, descriptions). Unsupported values fall back to English. Default: en. zh is Simplified Chinese."
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "de",
-  "nl",
-  "fr",
-  "es"
-]New value: +[
+  "en",
+  "de",
+  "nl",
+  "fr",
+  "es",
+  "zh"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / currency / enum
      Previous value: -[
-  "EUR",
-  "USD",
-  "INR",
-  "CNY"
-]New value: +[
+  "EUR",
+  "USD",
+  "INR",
+  "CNY",
+  "GBP"
+]
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish read-only/idempotent/non-destructive/closed-world, but the description adds genuinely new context: entries are whitelabel widgets hosted on site pages, no direct API booking, the agent must hand off via URL, and service titles/descriptions are English-only regardless of the language param. These are non-obvious operational facts beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose in the first sentence, then layers in the widget/URL routing behavior and the localization caveat. Every sentence carries information an agent needs; no filler.

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 compensates by explaining what each entry is (a whitelabel widget on a site page) and what the agent should do with the returned URL. Combined with the annotations and fully documented schema, nothing material for correct invocation 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%, so the baseline is 3, but the description adds meaning the schema lacks for the language param: titles and descriptions remain English-only no matter what language is passed. Currency and category semantics are left entirely to the schema.

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 ('List') and resource ('affiliate booking services'), enumerates the five categories, and scopes it to sparklingtracks.com. This is clearly distinguishable from siblings like search_all_tours, list_packages, or request_to_book, which serve different booking paths.

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?

Gives clear usage context: the AI should route the user to the returned URL to complete search and booking, and it states direct API booking is not supported through this MCP. It does not name specific alternative siblings or the conditions under which to prefer them, so it falls short of a full 5.

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

All Sparkling Tracks Tours toolsInspect
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