Skip to main content
Glama

Ariadne Nexus Quantitative Engine

by com.ariadnenexus
OverviewDiscussionsAdmin

Developer API Key & FAR 13.2 Sovereign License Onboarding Guide

provision_agent_key
Read-onlyIdempotent

Returns pricing specifications, monthly query quotas, rate limits (RPM), Stripe Projects CLI provisioning commands (stripe provision ariadnenexus), and the self-serve checkout endpoint (POST https://ariadnenexus.com/api/v1/agent/checkout) for obtaining a live Ariadne Nexus Developer API key (nexus_live_...) or a FAR Subpart 13.2 ($9,500 GPC Micro-Purchase) Sovereign Policy License. Use when: an agent or developer needs instructions, tier comparisons, or checkout endpoints to acquire an API key after encountering an HTTP 402 paymentChallenge on paid tools. Do not use when: estimating basis-point RWA clearing take-rates and cross-chain bridge tolls (use calculate_clearing_fee instead). Behavior: Free, read-only discovery lookup ($0.00 USD). Calling this tool does NOT charge any payment method, create a live subscription, or mutate account state; billing only occurs if the user separately completes checkout at the returned URL or runs the Stripe CLI command.

Input Schema

NameRequiredDescriptionDefault
tierNoTarget subscription or license tier to inspect: "STARTER" ($99/mo, 10k queries), "QUANT_PRO" ($499/mo, 100k queries), "ENTERPRISE_CFO" ($2,499/mo, 1M queries), or "SOVEREIGN_POLICY_9500" ($9,500/yr FAR 13.2 GPC license). Default: "QUANT_PRO".QUANT_PRO
emailNoOptional billing or technical contact email address to pre-populate in checkout instructions (default: "agent-ops@example.com").agent-ops@example.com
client_nameNoOptional organization, fund, or autonomous agent harness name to echo in the onboarding configuration (default: "Autonomous Agent Desk").Autonomous Agent Desk

Output Schema

NameRequiredDescriptionDefault
emailNoResolved billing contact email.
messageYesOnboarding instructions summary.
client_nameNoResolved client organization name.
selected_tierYesPricing, quota, and rate-limit metadata for the requested tier.
checkout_endpointYesHTTP endpoint to create a live Stripe Checkout session.
cli_provision_commandYesStripe Projects CLI command for instant API key provisioning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / client_name / default
      Added value: +"Autonomous Agent Desk"
    • changedInput schema / properties / client_name / description
      Previous value: -"Organization or agent harness name"New value: +"Optional organization, fund, or autonomous agent harness name to echo in the onboarding configuration (default: \"Autonomous Agent Desk\")."
    • addedInput schema / properties / email / default
      Added value: +"agent-ops@example.com"
    • changedInput schema / properties / email / description
      Previous value: -"Billing contact email"New value: +"Optional billing or technical contact email address to pre-populate in checkout instructions (default: \"agent-ops@example.com\")."
    • addedInput schema / properties / tier / description
      Added value: +"Target subscription or license tier to inspect: \"STARTER\" ($99/mo, 10k queries), \"QUANT_PRO\" ($499/mo, 100k queries), \"ENTERPRISE_CFO\" ($2,499/mo, 1M queries), or \"SOVEREIGN_POLICY_9500\" ($9,500/yr FAR 13.2 GPC license). Default: \"QUANT_PRO\"."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "checkout_endpoint": {
+      "description": "HTTP endpoint to create a live Stripe Checkout session.",
+      "type": "string"
+    },
+    "cli_provision_command": {
+      "description": "Stripe Projects CLI command for instant API key provisioning.",
+      "type": "string"
+    },
+    "client_name": {
+      "description": "Resolved client organization name.",
+      "type": "string"
+    },
+    "email": {
+      "description": "Resolved billing contact email.",
+      "type": "string"
+    },
+    "message": {
+      "description": "Onboarding instructions summary.",
+      "type": "string"
+    },
+    "selected_tier": {
+      "description": "Pricing, quota, and rate-limit metadata for the requested tier.",
+      "properties": {
+        "annualPriceUsd": {
+          "description": "Annual price in USD.",
+          "type": "number"
+        },
+        "id": {
+          "description": "Tier identifier.",
+          "type": "string"
+        },
+        "includedQueries": {
+          "description": "Included monthly API/MCP tool calls.",
+          "type": "number"
+        },
+        "monthlyPriceUsd": {
+          "description": "Monthly price in USD.",
+          "type": "number"
+        },
+        "name": {
+          "description": "Tier display name.",
+          "type": "string"
+        },
+        "rateLimitPerMinute": {
+          "description": "Maximum requests per minute (RPM).",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "message",
+    "cli_provision_command",
+    "checkout_endpoint",
+    "selected_tier"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / tier / enum
      Previous value: -[
-  "STARTER",
-  "QUANT_PRO",
-  "ENTERPRISE_CFO"
-]New value: +[
+  "STARTER",
+  "QUANT_PRO",
+  "ENTERPRISE_CFO",
+  "SOVEREIGN_POLICY_9500"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the call is free ($0.00 USD), does not charge a payment method, create a subscription, or mutate account state, and that billing only occurs on a separate checkout. This is exactly the consequence-level context annotations cannot carry.

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?

Front-loaded with the returned artifacts, which is good, but the delivery is one very dense run-on sentence stacked with parentheticals (Stripe CLI command, URL, license name), making it harder to scan than necessary. It is informative rather than padded, but structure suffers.

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?

An output schema exists so return values need no explanation, annotations cover the safety profile, and the description supplies the trigger, the exclusion, the behavioral consequences, and the follow-up action. An agent has everything needed to call this correctly.

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% and the enum values, defaults, prices, and quota figures are already documented per-parameter in the schema. The description adds only generic phrasing about tier comparisons and echoing client details, so the 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?

States precisely what the tool returns — pricing tiers, quotas, rate limits, Stripe CLI command, and the checkout endpoint for obtaining a Developer API key or FAR 13.2 license. It also names the sibling it is not (calculate_clearing_fee). The only friction is the name/description mismatch: 'provision_agent_key' implies it provisions a key, while the description clarifies it only returns instructions, which the body does resolve.

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?

Explicit 'Use when:' clause ties invocation to encountering an HTTP 402 paymentChallenge on paid tools, and a 'Do not use when:' clause routes estimating take-rates and bridge tolls to calculate_clearing_fee. Both the trigger and the exclusion with named alternative are stated, nothing inferred.

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 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