Skip to main content
Glama
dxpert-ai

dxpert: Industrial AI Agents for Manufacturing (OEE, Maintenance, Root Cause)

Official
by dxpert-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

start_purchase

Create a Stripe-hosted checkout URL for a dxpert Pro subscription or DX Roadmap plan. It charges nothing; the user opens the link and pays in a browser to attach access.

Instructions

Create a Stripe-hosted checkout URL for one dxpert product and return it. THIS CALL CHARGES NOTHING. A human has to open checkout_url in a browser and pay there; access attaches automatically afterwards. Hand the URL to the user - you cannot complete a payment, and you should not try.

Products: "pro" - dxpert Pro, a monthly subscription. Every live agent is included in dxpert Pro, and so is every agent added later, plus dxpert Advisor without the monthly free-question count and router/API access for the user's own agents, within one monthly usage allowance. Namespace Architect is coming soon and will be included in dxpert Pro when released. "roadmap" - DX Roadmap, a one-time, human-analyst-led, board-ready plan. Independent of dxpert Pro: it neither requires nor includes it. There is nothing else to buy: agents are never sold individually. Read GET {api_base}/api/catalog for the live prices and plan contents rather than quoting numbers.

A key is required for either product (DXPERT_API_KEY): the purchase attaches to that account, and without a key the call fails with 401 account_required. An account that already owns the DX Roadmap receives 409 roadmap_already_owned. Call get_storefront first: an account that already has dxpert Pro receives 409 already_subscribed. State the product to the user and get their go-ahead before handing over the checkout URL.

Input Schema

NameRequiredDescriptionDefault
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / product / enum
      Previous value: -[
-  "api",
-  "agents-all",
-  "roadmap",
-  "roadmap-bundle",
-  "shift-report",
-  "oee-narrator",
-  "alarm-triage",
-  "maintenance-copilot",
-  "root-cause",
-  "topup-50",
-  "topup-100"
-]New value: +[
+  "pro",
+  "roadmap"
+]
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: no charge occurs, a human must pay in a browser, access attaches automatically afterwards, a DXPERT_API_KEY is required, and specific failure modes (401 account_required, 409 roadmap_already_owned, 409 already_subscribed) are enumerated.

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?

Front-loaded with the most decision-relevant fact (no charge) and organized with a clear product breakdown. It is long, but nearly every sentence carries distinct operational value; slight trimming (e.g. the Namespace Architect aside) would not hurt.

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?

For a single-parameter purchase tool with no output schema, the description is complete: it explains the returned checkout_url, the human-in-the-loop flow, auth requirements, and all known error states.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: both enum values ('pro' subscription vs 'roadmap' one-time plan) are explained in detail, including that roadmap is independent of pro and that agents are never sold individually.

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 and resource: 'Create a Stripe-hosted checkout URL for one dxpert product and return it.' It also immediately clarifies the non-obvious scope ('THIS CALL CHARGES NOTHING'), which materially distinguishes it from a payment-completing tool.

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 sequencing and alternatives are given: 'Call get_storefront first,' 'State the product to the user and get their go-ahead before handing over the checkout URL,' and 'Read GET {api_base}/api/catalog ... rather than quoting numbers.' It also states what the agent should not do ('you cannot complete a payment, and you should not try').

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

Deploy Server

Other Tools