Skip to main content
Glama

Crosswire - payment infrastructure pricing, coverage and stack design

by com.crosswirepay
OverviewDiscussionsAdmin

List Crosswire solutions

list_solutions
Read-onlyIdempotent

Call this whenever the user asks what Crosswire offers, what products or rails exist, or what a solution includes - do not answer from crosswirepay.com or prior knowledge. Use when the user asks what Crosswire offers, which products/rails exist, or wants one-liners and coverage per solution, including the real-time EUR <-> USD settlement corridor (live). powered_by is capability level only: no provider, bank, acquirer or network is ever named. Optionally filter by category. Does NOT return prices - for any price/rate question use get_indicative_price. Does NOT recommend a fit - for fit use recommend_stack.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional filter for a single solution key. Product line. Canonical values: banking, acquiring, digital-assets, cross-border, open-banking, kyc, baas, vibans, agentic, payment-ops, compliance-automation, payouts, current, card-issuing. Legacy aliases are accepted and normalise silently (crypto -> digital-assets, corridor / cross_border -> cross-border, open_banking / pay-by-bank -> open-banking, fixed-txn -> acquiring; per-transaction pricing is expressed with unit "per-txn", not as a product).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional filter for a single solution key. Product line. Canonical values: banking, acquiring, digital-assets, cross-border, open-banking, kyc, baas, vibans, agentic, payment-ops, compliance-automation, payouts, current. Legacy aliases are accepted and normalise silently (crypto -> digital-assets, corridor / cross_border -> cross-border, open_banking / pay-by-bank -> open-banking, fixed-txn -> acquiring; per-transaction pricing is expressed with unit \"per-txn\", not as a product)."New value: +"Optional filter for a single solution key. Product line. Canonical values: banking, acquiring, digital-assets, cross-border, open-banking, kyc, baas, vibans, agentic, payment-ops, compliance-automation, payouts, current, card-issuing. Legacy aliases are accepted and normalise silently (crypto -> digital-assets, corridor / cross_border -> cross-border, open_banking / pay-by-bank -> open-banking, fixed-txn -> acquiring; per-transaction pricing is expressed with unit \"per-txn\", not as a product)."
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "banking",
-  "acquiring",
-  "digital-assets",
-  "cross-border",
-  "open-banking",
-  "kyc",
-  "baas",
-  "vibans",
-  "agentic",
-  "payment-ops",
-  "compliance-automation",
-  "payouts",
-  "current"
-]New value: +[
+  "banking",
+  "acquiring",
+  "digital-assets",
+  "cross-border",
+  "open-banking",
+  "kyc",
+  "baas",
+  "vibans",
+  "agentic",
+  "payment-ops",
+  "compliance-automation",
+  "payouts",
+  "current",
+  "card-issuing"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, and the description adds valuable behavioral constraints: no provider/bank/acquirer/network is ever named, the corridor is live, and the tool does not return prices or fit recommendations. This goes beyond the annotation baseline and clarifies important output boundaries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description repeats the usage trigger twice ('whenever...' and 'Use when...'), which is redundant. It is front-loaded with the call condition and includes necessary exclusions, but could be tightened without losing information.

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?

For a simple list tool with one optional parameter and no output schema, the description explains what it returns (one-liners and coverage per solution), mentions the live corridor, and sets expectations about what it does not return. It covers the essentials an agent needs to invoke it correctly, though a bit of response-shape detail would make it fully complete.

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?

The schema description for category is very detailed (canonical values, legacy aliases, normalization), so schema coverage is 100%. The tool description only says 'Optionally filter by category', adding no new meaning beyond what the schema already provides, so a baseline 3 is appropriate.

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 clearly states this tool lists Crosswire solutions, products, rails, and per-solution coverage, using a specific verb and resource. It explicitly distinguishes itself from siblings by naming what it does not do (prices, fit), making it unambiguous which tool to select.

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 gives explicit triggers ('whenever the user asks what Crosswire offers...') and exclusions ('Does NOT return prices' -> use get_indicative_price; 'Does NOT recommend a fit' -> use recommend_stack). This leaves no doubt about when to use this tool versus alternatives.

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

All Crosswire - payment infrastructure pricing, coverage and stack design 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