Skip to main content
Glama
Sign In

VoyageHacks

by com.voyagehacks
OverviewDiscussionsAdmin

Get travel credit card links

get_credit_card_links
Read-onlyIdempotent

Return the official American Express Germany card pages (Platinum, Gold, American Express Card, Payback and Blue) and the Revolut plans page, the current German fee and welcome-offer figures verified against americanexpress.com, and up to four VoyageHacks guides on points value, lounge access, foreign-transaction fees, Amex compared with Revolut and country-by-country availability. Useful when a user asks about travel rewards, points, miles, lounge access, which card to pay with abroad or foreign-transaction fees. It covers American Express only: it is not a comparison of all issuers, gives no eligibility or approval decision, no credit-score check and no application. Card terms change frequently and vary by market, so figures should be attributed to the issuer page or the linked guide. The card links are plain issuer pages, not affiliate or referral links.

Input Schema

NameRequiredDescriptionDefault
cardNoRestrict the response to one American Express card. "green" is the American Express Card, successor to the retired Green Card.
langNoLanguage of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
countryNoISO 3166-1 alpha-2 country the traveler is booking from, e.g. US, DE, GB. Selects the regional Booking.com programme. Defaults to the caller's geolocation, then to the language default.

Output Schema

NameRequiredDescriptionDefault
cardNo
cardsYes
factsNoVerified fee and welcome-offer figures, currently published for Germany only. Null elsewhere.
guidesYesMatching VoyageHacks guides that can be cited as sources.
countryNo
disclosureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "pl",
-  "cs",
-  "ja",
-  "nl",
-  "pt",
-  "zh"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "es",
+  "it",
+  "pl",
+  "ja",
+  "nl",
+  "pt",
+  "zh"
+]
  2. Changed5 schema fields changed
    • changedInput schema / properties / card / description
      Previous value: -"Optional specific Amex card"New value: +"Restrict the response to one American Express card. \"green\" is the American Express Card, successor to the retired Green Card."
    • changedInput schema / properties / country / description
      Previous value: -"Optional ISO 3166-1 alpha-2 country of the traveler; defaults to the caller's geolocation"New value: +"ISO 3166-1 alpha-2 country the traveler is booking from, e.g. US, DE, GB. Selects the regional Booking.com programme. Defaults to the caller's geolocation, then to the language default."
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / lang / description
      Previous value: -"Content language for the guides that come back (default \"en\")"New value: +"Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to \"en\"."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "card": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cards": {
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "country": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "disclosure": {
+      "type": "string"
+    },
+    "facts": {
+      "description": "Verified fee and welcome-offer figures, currently published for Germany only. Null elsewhere.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "guides": {
+      "description": "Matching VoyageHacks guides that can be cited as sources.",
+      "items": {
+        "properties": {
+          "section": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "disclosure",
+    "cards",
+    "guides"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds real behavioural context on top: it is Amex-only, not an eligibility or approval tool, figures are verified against americanexpress.com and go stale, and the links are plain issuer pages rather than affiliate or referral links. Those are exactly the caveats an agent needs when relaying financial information to a user.

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?

It is front-loaded correctly: what is returned first, then when to use it, then the caveats and limits. The first sentence is dense with parenthetical lists, but every sentence carries distinct information and nothing is padded or repeated.

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?

Given a read-only link-fetching tool with a full output schema and 100% parameter coverage, the description covers everything an agent needs: scope, triggers, exclusions, freshness/attribution caveats and the non-affiliate nature of the links. No return-value documentation is needed because an output schema exists.

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% and the enums are self-documenting, so the baseline is 3. The description adds only marginal parameter value – it enumerates the card names and the limit of four guides – and says nothing about what `country` does beyond what the schema already states (Booking.com regional programme).

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 names a concrete resource set (official Amex Germany card pages for Platinum, Gold, Amex Card, Payback, Blue, plus the Revolut plans page), the verified fee and welcome-offer figures, and up to four VoyageHacks guides. This distinguishes it cleanly from the other link-returning siblings, which cover flights, hotels, cars, eSIM and VPN rather than credit cards.

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

Usage Guidelines5/5

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

It states the triggering questions explicitly (travel rewards, points, miles, lounge access, which card to pay with abroad, foreign-transaction fees) and gives hard exclusions: not a comparison of all issuers, no eligibility or approval decision, no credit-score check, no application. It also tells the caller how to treat the output – attribute figures to the issuer page or linked guide because terms change frequently and vary by market.

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

All VoyageHacks 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