Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gyg_get_tour_reviews

Read-onlyIdempotent

Retrieve reviews for a GetYourGuide tour, including rating summary and individual reviews. Use compact view to strip image URLs or full view to include them.

Instructions

List customer reviews for a tour (rating outline plus individual review items). Image URLs are stripped by default; pass view:"full" to keep them.

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image URLs and keeps every other field; "full" returns GetYourGuide's whole record, image URLs included.
limitNoMaximum number of items to return (1-500).
offsetNoNumber of reviews to skip (0-based; the API caps review offsets at 300).
tourIdYesNumeric GetYourGuide tour ID (e.g. 23776).
currencyNoCurrency for prices, ISO 4217 (e.g. USD, EUR). Defaults to GYG_CURRENCY when set.
languageNoContent language (e.g. en, de). Defaults to GYG_LANGUAGE when set.
sortFieldNoSort field for reviews.
sortDirectionNoSort direction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.7
    • 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 URLs and keeps every other field; \"full\" returns GetYourGuide's whole record, image URLs included.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  2. 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"
  3. First observedv1.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds one genuine behavioural fact — image URLs are stripped by default — but says nothing about ordering defaults, offset capping, or rate limits. Some added value, but it also largely repeats the view parameter already spelled out in the schema.

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?

Two tight sentences with the primary purpose front-loaded and the notable default (image stripping) immediately after. No filler, though the second sentence is partially redundant with the schema's view description.

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 no output schema but full schema coverage on 8 parameters, the description covers purpose, default response shape, and the key opt-in. An agent can call this correctly; only sorting defaults and large-result traversal guidance are absent.

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%, so all 8 parameters including the compact/full semantics, limit bounds and the offset-300 cap are already documented. The description only restates the view toggle, adding no syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ("List customer reviews for a tour") with the response shape noted. The resource is clearly distinct from siblings like gyg_get_tour or gyg_get_tour_options, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one actionable condition (pass view:"full" to keep image URLs), but says nothing about when to choose this over gyg_get_tour for review data, nor about pagination behaviour for walking large review sets. Usage is implied by the tool's scope rather than stated.

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