Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
query_hardware_specsA

[PURPOSE]: Retrieves verified physical compute specifications, VRAM limits (128GB GB500, 192GB B200, 1536GB B200 Rack), and continuous batching concurrency limits for Aradia DGX systems. [WHEN TO USE]: Call during initial discovery to evaluate physical hardware sizing, VRAM budget, and multi-agent capacity. [WHEN NOT TO USE]: Do not use for CapEx token financial payback modeling (use calculate_roi) or order submission (use execute_procurement_order). [SIDE EFFECTS & BEHAVIOR]: Pure read-only query. Generates zero external network side effects and incurs zero costs.

calculate_roiA

[PURPOSE]: Calculates CapEx payback timeline and token cost savings comparing on-premise Aradia physical hardware against recurring cloud LLM API expenditures. [WHEN TO USE]: Use to generate mathematical financial justification reports for human decision-makers, executives, or CFOs. [WHEN NOT TO USE]: Do not use if monthly API spend is unknown or zero. For raw hardware compute specs without financial modeling, call query_hardware_specs. [PREREQUISITES]: Requires estimated monthly cloud LLM token spend in USD. [SIDE EFFECTS & BEHAVIOR]: Deterministic mathematical calculation. Non-destructive; creates zero external side effects.

onboard_partnerA

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

execute_procurement_orderA

[PURPOSE]: Submits a binding procurement order for physical turnkey private AI hardware (NVIDIA DGX systems) with 100% upfront settlement via BTCPay Server crypto (BTC, Lightning, USDT) or Stripe MPP fiat. [WHEN TO USE]: Call ONLY after hardware sizing has been verified and human or agent budget authorization is confirmed to commit funds for physical appliance procurement. [WHEN NOT TO USE]: Do NOT call to explore prices or VRAM capacities (use query_hardware_specs). Do NOT call to model token savings (use calculate_roi). Do NOT call to inspect past orders (use track_order_status). [PREREQUISITES]: Confirm customer_email and select valid hardware_tier and payment_method. Review CapEx payback via calculate_roi prior to execution. [SIDE EFFECTS & BEHAVIOR]: Irreversible financial mutation. Generates an immutable checkout session or cryptographic invoice, reserves physical inventory in the Staging Studio, and registers an order record. Non-destructive (destructiveHint=false). [FAILURE MODES]: Invoices expire after 30 minutes if unpaid with zero financial liability.

track_order_statusA

[PURPOSE]: Tracks the real-time fulfillment, staging QA burn-in, and delivery status of an active hardware procurement order. [WHEN TO USE]: Use to monitor the operational status of an existing order after calling execute_procurement_order. [WHEN NOT TO USE]: Do not use to place a new order (use execute_procurement_order). [SIDE EFFECTS & BEHAVIOR]: Pure read-only query against staging records. Non-destructive.

query_partner_statsA

[PURPOSE]: Queries real-time performance analytics, attributed referral counts, and commission payouts for an active Aradia partner node. [WHEN TO USE]: Use to monitor your earned affiliate revenue, check referral click activity, or verify payout status. [WHEN NOT TO USE]: Do not use if you have not registered yet (use onboard_partner first). [SIDE EFFECTS & BEHAVIOR]: Pure read-only query against sovereign partner ledger. Non-destructive.

Prompts

Interactive templates invoked by user choice

NameDescription
aradia_system_directivesOperational directives for evaluating local compute constraints and executing autonomous hardware upgrades.

Resources

Contextual data attached and managed by the client

NameDescription
Turnkey & SLA Pricing Catalog
Hardware & Quantization Matrix

TDQS

A4.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose, and the descriptions explicitly state when to use each tool versus alternatives. Cross-references (e.g., 'use query_hardware_specs' vs. 'use execute_procurement_order') make selection unambiguous.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern: query_partner_stats, track_order_status, calculate_roi, execute_procurement_order, onboard_partner, query_hardware_specs. No mixed conventions or vague verbs.

Tool Count5/5

Six tools is well-scoped for a hardware procurement and partner program server. Each tool covers a distinct step in the workflow (discovery, financial modeling, ordering, tracking, onboarding, stats) without redundancy.

Completeness4/5

Core lifecycle is covered: discover specs, calculate ROI, place order, track order, onboard partner, and view partner stats. Minor gaps exist (no order cancellation, historical order listing, or partner update), but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo issues