Verdonz MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERDONZ_MOCK | No | Set to true to use fictional demo data without a network connection. | |
| VERDONZ_API_KEY | No | Your Verdonz API key. | |
| VERDONZ_BASE_URL | No | The base URL of the Verdonz API. Required in production mode. |
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 |
|---|---|
| verdonz_list_metricsC | List governed metric definitions the identity can access. |
| verdonz_get_metricC | Get the definition and metadata for a governed metric. |
| verdonz_list_datasetsC | List governed datasets/data sources available to the identity. |
| verdonz_askC | Ask a business question through Verdonz governed semantic data. |
| verdonz_investigateC | Investigate why a governed metric changed. Production availability depends on the connected Verdonz API. |
| verdonz_get_evidenceC | Retrieve source/lineage evidence for a Verdonz result when supported. |
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 6 tools
list_metrics/get_metric and list_datasets are clearly distinct, and get_evidence is a well-separated retrieval role. verdonz_ask and verdonz_investigate are the closest pair, but the descriptions (business question vs. root-cause investigation) give enough signal to separate them.
All tools share the verdonz_ prefix and use a consistent verb-first style (list_, get_, ask, investigate). Minor deviation: ask and investigate omit the noun object that the other four include, but the pattern remains readable and predictable.
Six tools is well-scoped for a governed semantic-data Q&A surface, with each tool earning its place (two listers, two getters, one ask, one investigate). Nothing feels padded or missing at this granularity.
Covers the core read lifecycle: discover datasets and metrics, ask questions, investigate metric changes, and pull evidence/lineage. Minor gaps around deeper lineage traversal or metric comparison exist, but agents can work around them via ask/investigate.