AI Data Marketplace
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_marketplace_productsA | Free discovery tool. Rank the live DopamineDesk x402 catalog against a plain-language buyer task before choosing or paying for a product. |
| purchase_marketplace_productA | Use after find_marketplace_products. Preview or purchase the selected paid product by its operation_id, without searching through the full dynamic tool list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one for discovery/search and one for purchasing. No overlap or confusion.
Both tools follow a consistent verb_noun pattern ('find_marketplace_products' and 'purchase_marketplace_product'), with only a minor plural/singular difference that is contextually appropriate.
With only two tools, the set feels minimal for a marketplace. While it covers the core discovery and purchase flow, it may be slightly thin for a full-featured marketplace, but it is not unreasonably sparse.
The tools cover the basic buyer journey (find and purchase), but lack other expected marketplace operations such as viewing product details, managing orders, or handling refunds. This leaves notable gaps for a complete marketplace experience.