Skip to main content
Glama

Caelara Labs Global Locale

cross_border_checkout_composite

Cross-border checkout quote: FX conversion into the destination currency, VAT/GST, postal-code validation and EU reverse-charge eligibility

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": "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 observed

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 behavioral burden. Calling it a 'quote' usefully signals it prices rather than charges, and the listed components disclose what is computed, but it says nothing about side effects, permissions, FX rate freshness or validity window, or failure behavior when postal-code validation fails.

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?

A single dense sentence with the core purpose front-loaded and zero filler. It is a noun phrase rather than a complete sentence, but every clause maps to a real computed output and nothing is redundant.

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?

For a seven-parameter financial composite with no annotations and no output schema, the description covers the computation scope but not the return shape, whether the quote is time-bound, or what happens on partial failure. It is adequate to decide to call the tool but leaves real gaps for correct interpretation of results.

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 every parameter is already documented in the input schema, including the vat_id note about format-only screening. The description adds only indirect mapping — reverse-charge eligibility implies vat_id and origin_country, postal validation implies postal_code — without new syntax or format detail. 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?

The description names a specific composite resource — a cross-border checkout quote — and enumerates its four components: FX conversion, VAT/GST, postal-code validation, and EU reverse-charge eligibility. It is clear what the tool produces, but it does not distinguish itself from the individual sibling calculators such as live_fx_rates or vat_gst_rate_lookup.

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' — an agent can infer this is for pricing an international order. There is no explicit guidance on when to prefer this composite over calling the individual FX, VAT, and postal-code tools, and no stated preconditions or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources