data-marketplace-mcp-server
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| marketplace_overviewB | Übersicht über den internen Data Marketplace und seine Basisfunktionen. |
| search_data_productsA | Datenkatalog durchsuchen — wie Produktsuche im internen Marktplatz. Args: query: Freitext (z. B. 'Kundenhistorie Kündigungen'). region: Region filtern (z. B. 'DACH'). certified_only: Nur zertifizierte/verifizierte Produkte. domain: Fachdomäne (z. B. 'sales', 'marketing'). limit: Maximale Trefferzahl. |
| get_data_productB | Metadaten, Ownership, Zertifizierung und Governance eines Datenprodukts laden. |
| preview_data_productB | Anonymisierte Datenvorschau und Spalten-Profiling für ein Datenprodukt. |
| get_product_lineageC | Data Lineage (Daten-Stammbaum) für ein Produkt — inkl. Atlas wenn konfiguriert. |
| search_glossaryB | Business Glossary durchsuchen — übersetzt technische Begriffe für Business-Nutzer. |
| request_data_accessA | Zugriff anfordern / abonnieren — registriert Subscriber im Data Contract consumer-Attribut (Atlas). Wenn MARKETPLACE_USE_DATA_CONTRACT_SUBSCRIBERS=true (Default), wird kein lokaler Subscriber-Datensatz angelegt; der Data Contract ist Single Source of Truth. Args: product_id: z. B. DP-MART-CREDIT-QUALITY-MATRIX requester: E-Mail oder User-ID der antragstellenden Person purpose: Nutzungszweck (DSGVO/Revision) project: Projektname duration_months: Zugriffsdauer in Monaten target_environment: Zielumgebung (z. B. marketing-snowflake) |
| list_access_requestsC | Subscriber/Zugriffsanfragen auflisten. Im Data-Contract-Modus werden consumer-Einträge aus dem governing data_contract gelesen. |
| list_product_subscribersC | Subscriber eines Datenprodukts aus dem governing Data Contract lesen. |
| approve_access_requestC | Zugriffsanfrage genehmigen und automatisches Provisioning anstoßen. |
| reject_access_requestC | Zugriffsanfrage ablehnen. |
| publish_data_productC | Neues Datenprodukt registrieren (Data Publishing Wizard für Data Owner). |
| certify_data_productB | Qualitätssiegel setzen (verified, certified, deprecated). |
| submit_product_feedbackD | Sterne-Feedback zur Datenqualität abgeben (1–5). |
| ensure_data_marketplace_typedefB | Register or upgrade the data_marketplace_product entity typedef in Atlas (serviceType: data_mesh). WRITE OPERATION |
| sync_data_product_to_atlasA | Sync marketplace product(s) to Atlas as data_marketplace_product entities. WRITE OPERATION Args: product_id: Optional product ID. If omitted, syncs all local marketplace products. link_dataset: Link each product to its underlying Atlas dataset when atlas_qualified_name is set. |
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 16 tools
Most tools have clearly distinct purposes: searching, viewing, requesting access, publishing, and sync operations cover separate concerns. However, list_access_requests and list_product_subscribers both deal with subscribers/access and could cause some confusion about which to use for a given scenario.
The naming follows a strong verb_noun pattern (search_data_products, get_data_product, preview_data_product, publish_data_product, certify_data_product). Minor deviations exist: ensure_data_marketplace_typedef and get_product_lineage break the strict pattern but are still readable and descriptive.
At 16 tools, this sits slightly above the ideal sweet spot but is reasonable for a marketplace with search, product lifecycle, access management, and Atlas sync capabilities. Most tools earn their place, though the two ‘WRITE OPERATION’ Atlas sync tools are somewhat operational rather than user-facing.
The surface covers search, view, preview, lineage, glossary, access lifecycle (request/list/approve/reject), publishing, certification, and feedback. Minor gaps include no explicit update/delete for data products (only publish/create) and subscription management beyond listing, but the core marketplace workflow is well covered.