Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_geo_cross_border_checkout_composite

Converts order amounts to the destination currency and calculates VAT/GST, postal-code validation, and EU reverse-charge eligibility for cross-border checkout quotes.

Instructions

[Global Locale] Cross-border checkout quote: FX conversion into the destination currency, VAT/GST, postal-code validation and EU reverse-charge eligibility Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://geo.caelaralabs.com.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "<amount>",
      "currency": "<currency>",
      "country": "<country>"
    },
    "name": "caelara_geo_cross_border_checkout_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesOrder subtotal in the source currency
vat_idNoBuyer VAT ID for B2B reverse-charge screening (format only, not VIES-verified)
countryYesDestination country (ISO alpha-2, e.g. DE)
currencyYesSource currency ISO 4217 code, e.g. USD
postal_codeNoDestination postal code to validate
origin_countryNoSeller country (ISO alpha-2) for reverse-charge screening
prices_include_taxNotrue when the amount already includes tax

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does contribute real behavioral context beyond structured data: measured p50 12 ms / p95 14 ms with a benchmark date and the upstream endpoint host. However, it never states that the call is a side-effect-free read/quote, whether it consumes credits or requires a key, or what happens when inputs fail screening — gaps that matter for an unannotated tool.

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?

Purpose is front-loaded in the first clause, followed by the capability list, the latency footnote and the endpoint. Three sentences with little waste; the benchmark parenthetical is arguably the least essential element but is still operationally useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven parameters, three required, no annotations and no output schema, the definition should describe the shape of the returned quote. It implies what is computed but never lists the returned fields, nor explains whether an invalid postal code or ineligible reverse charge fails the call or is reported as a flag.

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 coverage is 100%, so the schema already explains every parameter, making 3 the baseline. The description does map its four computations onto the relevant inputs (currency/country for FX, vat_id plus origin_country for reverse charge, postal_code for validation), but it leaves ambiguity on prices_include_tax and refers to conversion 'into the destination currency' while the currency parameter is explicitly the source currency.

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?

The description names a specific resource (a cross-border checkout quote) and enumerates the four computations it bundles: FX conversion, VAT/GST, postal-code validation and EU reverse-charge screening. That is enough for an agent to know what it produces, but it does not distinguish this composite from the single-purpose siblings it aggregates (live_fx_rates, vat_gst_rate_lookup, postal_code_validator).

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?

Usage is only implied by the phrase 'Cross-border checkout quote', which suggests the checkout/total-price use case. There is no explicit when-to-use versus when-not statement, no mention of when to prefer the individual geo tools, and no stated prerequisites such as required auth or a country/currency pair constraint.

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