Skip to main content
Glama

Korea Import Customs Duty & Cross-Border Payout MCP

Compare Cross-Border Freelancer & B2B Payout Fees

compare_crossborder_payout_fees
Read-onlyIdempotent

Compares net USD and KRW take-home pay across USDC L2 settlement, Wise mid-market FX, SWIFT bank wires, and PayPal invoices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_crossborder_payout_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_usdNoInvoice amount in USD (default 2500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety and side-effect behavior is covered. The description adds useful scope detail — which four settlement rails and which two output currencies are compared — but for a fee/FX tool it omits what matters most behaviorally: whether rates are live or estimated, their freshness, and whether the comparison assumes any particular FX spread or fee schedule.

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?

One sentence, front-loaded with the verb and the full comparison scope, with every clause earning its place by naming a distinct settlement rail. No filler, no restatement of the title.

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?

The tool is simple (one optional param, rich annotations), but with no output schema the description should say what actually comes back — a per-rail fee breakdown, effective FX rate, net amount — and whether results are estimates or live quotes. As written, an agent knows what the tool compares but not what it returns or how much to trust it.

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% and the single optional parameter documents both its meaning (invoice amount in USD) and its default (2500), so the schema carries the load. The description adds nothing about the parameter — notably it does not clarify the USD-to-KRW conversion assumption that its stated KRW output implies.

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 verb ('Compares') and a precisely enumerated resource: net USD and KRW take-home pay across four named rails (USDC L2, Wise mid-market, SWIFT, PayPal invoices). It is unmistakably distinct from the only sibling, calculate_korea_import_customs, though it never explicitly contrasts itself with it.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated preconditions, and no routing advice toward or away from an alternative. The agent must infer usage purely from the concept of 'take-home pay comparison', and the 'Freelancer & B2B' audience framing lives only in the title, not the description.

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.