aradia-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

onboard_partner

Register an AI agent or operator into the Aradia Partner Program to earn hardware bounties and recurring SLA commissions, creating a Stripe payout account and tracking ref code.

Instructions

[PURPOSE]: Registers an autonomous AI agent or human operator into the Aradia Partner Program to earn 10% hardware bounties ($1,512 to $50,550 USD) and 10% recurring monthly SLA commissions. [WHEN TO USE]: Call ONCE when an agent or operator wants to establish an affiliate revenue node, acquire a ?ref= tracking ID, and generate treasury revenue to self-fund compute upgrades. [WHEN NOT TO USE]: Do NOT call to purchase equipment (use execute_procurement_order). Do NOT call if you already have a partner ref_code (use query_partner_stats). [PREREQUISITES]: Requires a valid contact email for Stripe Express payout account linking. [SIDE EFFECTS & BEHAVIOR]: State-mutating operation. Creates an external Stripe Express Connected Account entity, registers a 4-character code in Aradia's ledger, and triggers a verification email. Non-destructive.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country`	No	ISO 3166-1 alpha-2 country code for banking payouts (default: 'US').	US
`entity_name`	Yes	Operating name, legal brand, or digital handle of the agent or operator (e.g. 'Autonomous-Finance-Agent').
`contact_email`	Yes	Valid RFC 5322 email address of the operator or treasury manager to receive the Stripe Express onboarding link and commission notices.

Output Schema

TableJSON Schema

Name	Required	Description
`ref_code`	Yes	Unique 4-character referral code (e.g. '5FYVQ').
`partner_id`	No	Stripe Connected Account identifier.
`referral_url`	Yes	Attributed referral link for embedding in agent recommendations.
`onboarding_url`	Yes	Stripe Express verification link to link payout bank accounts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Sep 13, 2026

addedInput schema / properties / contact_email / description

Added value: +"Valid RFC 5322 email address of the operator or treasury manager to receive the Stripe Express onboarding link and commission notices."

addedInput schema / properties / country

Added value: +{
+  "default": "US",
+  "description": "ISO 3166-1 alpha-2 country code for banking payouts (default: 'US').",
+  "type": "string"
+}

addedInput schema / properties / entity_name / description

Added value: +"Operating name, legal brand, or digital handle of the agent or operator (e.g. 'Autonomous-Finance-Agent')."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "onboarding_url": {
+      "description": "Stripe Express verification link to link payout bank accounts.",
+      "type": "string"
+    },
+    "partner_id": {
+      "description": "Stripe Connected Account identifier.",
+      "type": "string"
+    },
+    "ref_code": {
+      "description": "Unique 4-character referral code (e.g. '5FYVQ').",
+      "type": "string"
+    },
+    "referral_url": {
+      "description": "Attributed referral link for embedding in agent recommendations.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ref_code",
+    "referral_url",
+    "onboarding_url"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare it is not read-only and not destructive. The description adds rich behavioral context: it creates an external Stripe Express Connected Account entity, registers a code in the ledger, triggers a verification email, and requires a valid contact email for payout linking. This exceeds what annotations provide.

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?

The labeled-section structure ([PURPOSE], [WHEN TO USE], etc.) is front-loaded and scannable, with no wasted sentences. Slightly verbose due to the monetary figures, but each section earns its place.

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?

Given the mutation with external side effects, the description covers prerequisites, state changes, user-visible consequences (verification email), and routing to siblings. The output schema exists, so return-value detail is rightly omitted.

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%, so the schema already fully documents all three parameters including defaults and examples. The description mentions the contact email requirement but adds no syntax or format details beyond the schema, so baseline 3 applies.

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?

States a specific verb (Registers) and resource (autonomous AI agent or human operator into the Aradia Partner Program), plus the value proposition. It clearly distinguishes itself from siblings by naming execute_procurement_order and query_partner_stats as alternatives.

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?

Explicitly states when to use (ONCE when establishing an affiliate revenue node) and when not to use, naming the exact alternative tools for purchase and existing-partner scenarios. The 'Call ONCE' cadence is a concrete usage constraint.

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

Deploy Server