F
licenseA
qualityC
maintenanceEnables load testing and validation of an order API by generating synthetic orders, previewing them, and sending batches while enforcing guardrails like bounded counts and fixed seeds for replay.
3
-
ecommerce-oltp
Related Servers
Alternatives to ecommerce-oltp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGenerates and deploys Cloudera Data Engineering (CDE) Airflow jobs from ODCS data contracts, validating live table data in CDW against schema and data-quality rules without WAP staging.13Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to investigate and safely resolve commerce order exceptions, such as expired inventory reservations, by providing a workflow across synthetic order, payment, inventory, and fulfillment systems.-
- FlicenseNot gradedqualityCmaintenanceProvides deterministic mock customer health, product usage, and recommended playbook data via three MCP tools for a Customer Success Orchestrator demo.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to explore and query a mock e-commerce store's data including customers, products, inventory, and orders through conversational interactions backed by PostgreSQL.-
- FlicenseNot gradedqualityDmaintenanceEnables simulating customer orders from a dummy restaurant menu and tracking their status in real-time via RESTful APIs.-
TDQS
B3.4/5.0
Scored across 9 tools
Disambiguation4/5
Most tools have clearly distinct roles: generation, ETL, fraud case listing/execution, and querying. The main ambiguity is between run_fraud_case and run_fraud_agent_cases, but their descriptions clarify single-case versus agent-owned case batches.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern, with recognizable prefixes like run_, list_, generate_, etl_star_, and query_. This makes the tool surface predictable and easy to navigate.
Tool Count5/5
Nine tools is a well-scoped size for this server's purpose. Each tool covers a distinct phase of the workflow—data generation, ETL, fraud case evaluation, and querying—without unnecessary redundancy.
Completeness4/5
The core lifecycle of generating OLTP data, building star-schema artifacts, running fraud cases, and querying results is well covered. Minor gaps include the lack of explicit schema/reset management or direct row-level CRUD, but agents can work around these using query_dataset and generation tools.
Maintenance
ActivityMaintained
ResponsivenessNo issues