Ariadne Nexus Quantitative Engine

Institutional RWA Clearing Take-Rate & Bridge Fee Calculator

calculate_clearing_fee

Read-onlyIdempotent

Calculates institutional RWA clearing house take-rates (in basis points and USD), cross-chain settlement bridge tolls, platform SaaS subscription fees, and net annual clearing cost projections across Ariadne Nexus membership tiers. Use when: estimating monthly or annual clearing fees, basis-point take-rates, and cross-chain bridge settlement costs before syndicating an RWA vault or selecting an institutional billing tier. Do not use when: provisioning an API key or generating a live Stripe checkout session (use provision_agent_key instead), or valuing bond CUSIPs (use get_cusip_valuation instead). Behavior: Free, open-access, read-only deterministic calculator ($0.00 USD; requires no apiKey or paymentToken and performs no external network calls or billing mutations).

Input Schema

Name	Required	Description	Default
`tier`	No	Institutional membership tier governing base SaaS fee and clearing take-rate bps discount (e.g., "QUANT_PRO", "INSTITUTIONAL_GOLD", "SOVEREIGN_PRIME"; default: "QUANT_PRO").	QUANT_PRO
`billing_interval`	No	Subscription billing cycle used to calculate platform base fee discounts ("monthly" or "annual"; default: "monthly").	monthly
`bridge_volume_usd`	No	Projected monthly cross-chain bridge settlement volume (Base / Solana / Tempo USDC) in USD (e.g., 2500000 for $2.5M/month; default: 2500000).
`clearing_volume_usd`	No	Projected monthly gross RWA transaction volume settled through the clearing house in USD (e.g., 10000000 for $10M/month; default: 10000000).

Output Schema

Name	Required	Description
`tier`	Yes	Selected institutional membership tier identifier.
`tierName`	No	Human-readable institutional tier title.
`bridgeFeeUsd`	Yes	Monthly cross-chain bridge fee in USD.
`bridgeTollBps`	No	Applied cross-chain bridge settlement toll in basis points.
`billingInterval`	No	Applied billing interval.
`bridgeVolumeUsd`	No	Monthly cross-chain bridge volume in USD.
`clearingVolumeUsd`	Yes	Monthly RWA clearing volume in USD.
`baseSubscriptionUsd`	No	Recurring platform subscription fee in USD.
`clearingTakeRateBps`	No	Applied clearing take-rate in basis points (1 bp = 0.01%).
`clearingTakeRateUsd`	Yes	Monthly clearing take-rate fee in USD.
`annualizedRunRateUsd`	No	Annualized 12-month total clearing and platform fee projection in USD.
`totalMonthlyRevenueUsd`	Yes	Total combined monthly platform + clearing + bridge fee in USD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 19, 2026

addedInput schema / properties / billing_interval / description

Added value: +"Subscription billing cycle used to calculate platform base fee discounts (\"monthly\" or \"annual\"; default: \"monthly\")."

changedInput schema / properties / bridge_volume_usd / description

Previous value: -"Monthly cross-chain bridge volume in USD"New value: +"Projected monthly cross-chain bridge settlement volume (Base / Solana / Tempo USDC) in USD (e.g., 2500000 for $2.5M/month; default: 2500000)."

changedInput schema / properties / clearing_volume_usd / description

Previous value: -"Monthly settled transaction volume in USD"New value: +"Projected monthly gross RWA transaction volume settled through the clearing house in USD (e.g., 10000000 for $10M/month; default: 10000000)."

addedInput schema / properties / tier / description

Added value: +"Institutional membership tier governing base SaaS fee and clearing take-rate bps discount (e.g., \"QUANT_PRO\", \"INSTITUTIONAL_GOLD\", \"SOVEREIGN_PRIME\"; default: \"QUANT_PRO\")."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "annualizedRunRateUsd": {
+      "description": "Annualized 12-month total clearing and platform fee projection in USD.",
+      "type": "number"
+    },
+    "baseSubscriptionUsd": {
+      "description": "Recurring platform subscription fee in USD.",
+      "type": "number"
+    },
+    "billingInterval": {
+      "description": "Applied billing interval.",
+      "enum": [
+        "monthly",
+        "annual"
+      ],
+      "type": "string"
+    },
+    "bridgeFeeUsd": {
+      "description": "Monthly cross-chain bridge fee in USD.",
+      "type": "number"
+    },
+    "bridgeTollBps": {
+      "description": "Applied cross-chain bridge settlement toll in basis points.",
+      "type": "number"
+    },
+    "bridgeVolumeUsd": {
+      "description": "Monthly cross-chain bridge volume in USD.",
+      "type": "number"
+    },
+    "clearingTakeRateBps": {
+      "description": "Applied clearing take-rate in basis points (1 bp = 0.01%).",
+      "type": "number"
+    },
+    "clearingTakeRateUsd": {
+      "description": "Monthly clearing take-rate fee in USD.",
+      "type": "number"
+    },
+    "clearingVolumeUsd": {
+      "description": "Monthly RWA clearing volume in USD.",
+      "type": "number"
+    },
+    "tier": {
+      "description": "Selected institutional membership tier identifier.",
+      "type": "string"
+    },
+    "tierName": {
+      "description": "Human-readable institutional tier title.",
+      "type": "string"
+    },
+    "totalMonthlyRevenueUsd": {
+      "description": "Total combined monthly platform + clearing + bridge fee in USD.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "tier",
+    "clearingVolumeUsd",
+    "clearingTakeRateUsd",
+    "bridgeFeeUsd",
+    "totalMonthlyRevenueUsd"
+  ],
+  "type": "object"
+}

First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds practical context the annotations cannot express: the tool is free ($0.00 USD), requires no apiKey or paymentToken, and makes no external network calls or billing mutations. For a fee/billing-adjacent tool, that auth-and-cost disclosure is exactly the information an agent needs to avoid misrouting a paid provisioning flow.

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?

Front-loaded with the verb and output set, then cleanly segmented into 'Use when', 'Do not use when', and 'Behavior' blocks. Every sentence carries routing, scoping, or cost/auth information; no filler.

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?

With an output schema present, return values need no explanation, and the description covers purpose, routing, prerequisites, and cost. For a zero-required-param, deterministic calculator with full schema coverage, nothing needed to invoke it correctly is missing.

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% with enum values and defaults fully documented, so the schema carries the parameter burden and baseline 3 applies. The description only gestures at tiers and basis points without adding units, ranges, or interaction semantics beyond the schema; note the param description's example value 'SOVEREIGN_PRIME' does not appear in the enum, but that is a schema-side inconsistency, not a gap the description was obligated to fix.

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 opening sentence names a specific verb (Calculates) plus four concrete outputs: clearing take-rates in bps and USD, cross-chain bridge tolls, SaaS subscription fees, and net annual clearing cost projections. This is unmistakably distinct from siblings like provision_agent_key or get_cusip_valuation, which the description also names explicitly.

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 provides an explicit 'Use when' clause (estimating monthly/annual clearing fees, bps take-rates, bridge settlement costs before syndicating a vault or choosing a billing tier) and an explicit 'Do not use when' clause that routes to two named alternative tools. Nothing is left to inference.

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

All Ariadne Nexus Quantitative Engine tools Inspect

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

Need Help?