Skip to main content
Glama
chrischall

viator-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vt_get_exchange_rates

Read-only

Retrieve exchange rates for currencies Viator supports so you can convert supplier-currency prices from availability schedules into your desired currency. Cached reference data keeps conversions accurate.

Instructions

Get exchange rates between currencies Viator supports — needed to convert supplier-currency prices from vt_get_availability_schedule. Reference data — cached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns Viator's payload untouched. No field projection on this tool — every other field comes back as Viator sent it.
source_currenciesNoSource currency codes (e.g. ["EUR"])
target_currenciesNoTarget currency codes (e.g. ["USD"])

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.2.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Viator's payload untouched. No field projection on this tool — every other field comes back as Viator sent it.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv1.0.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value with 'Reference data — cached', which discloses that rates are cached reference data rather than live quotes, informing expectations about freshness. This is a useful behavioral addition beyond the structured annotations.

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?

Two short, telegraphic sentences front-load the purpose, then add the integration hint and caching note. There is no filler; every clause either clarifies scope or gives behavioral context.

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?

With only three well-documented parameters, read-only/open-world annotations, and no output schema, the description covers the essential 'why' (price conversion after availability schedule) and 'what to expect' (cached reference data). The only minor gap is the absence of a note about default behavior when source/target arrays are omitted, but the schema's clarity keeps this from being a substantial shortfall.

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 description coverage is 100%: the view parameter has a detailed response-shape explanation, and source_currencies/target_currencies both provide enum lists and examples. The description itself adds no parameter-level detail, but the schema fully documents the parameters, so baseline 3 is appropriate.

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 states a specific verb and resource: 'Get exchange rates between currencies Viator supports'. It also ties the purpose to a concrete downstream use case ('needed to convert supplier-currency prices from vt_get_availability_schedule'), which distinguishes it clearly from every sibling tool, all of which are about products, attractions, destinations, or health.

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 description explicitly tells the agent when this tool is needed: after vt_get_availability_schedule, to convert supplier-currency prices. While it doesn't list alternatives or when-not-to-use conditions, no sibling appears to offer exchange rates, so the provided context is a clear and sufficient directive.

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