dataville-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATAVILLE_API_KEY | Yes | Your Dataville API key, obtainable from the Dataville dashboard | |
| DATAVILLE_API_BASE_URL | No | Optional base URL for the Dataville API; set to http://localhost:5000 for local development | https://api.dataville.com |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dataville_sourcesA | List every Dataville data source with a one-line description and the SQL tables (if any) that query_dataville can read for it. Call describe_dataville_source for a source's keyword format and table columns. |
| describe_dataville_sourceA | Show how to use one data source: what search_dataville expects as keywords (with an example that returns a result), and the SQL tables and columns query_dataville can read for it. Sources with no tables can only be searched. |
| search_datavilleA | Look up one thing in a Dataville data source by keywords and get back the single best-matching record (full text in |
| query_datavilleA | Run a read-only SQL SELECT (DuckDB dialect) over Dataville's stored tables: wiki, arxiv, gutenberg, fooddata, pwc_methods, pwc_datasets, edgar, openalex, pypi, stackexchange. Use it to list, filter (WHERE … ILIKE '%term%'), sort, count, aggregate, or join across sources, and page through results with LIMIT/OFFSET. Get each table's columns from describe_dataville_source. Only SELECT is allowed; at most 1,000 rows are returned (a missing LIMIT becomes LIMIT 1000); queries time out after 30 s. Billed per row returned, so keep LIMIT as small as the task allows. The tables hold Dataville's stored copy: some sources are loaded in bulk, others only hold records fetched before, so a row missing here may still exist upstream — fall back to search_dataville for a specific item. |
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 4 tools
Each tool targets a distinct phase of the workflow: list sources, describe a source, keyword search for one record, and SQL query for many records. The descriptions explicitly contrast search_dataville vs query_dataville, leaving no overlap.
All names are snake_case with a clear verb prefix (list_, describe_, search_, query_), but the position of 'dataville' varies slightly (list_dataville_sources vs search_dataville). Still predictable and readable.
Four tools is a lean but well-scoped set for a read-only data access server; each tool earns its place. It is slightly on the thin side (no dedicated fetch-by-id or schema tool), but nothing feels redundant.
Discovery (list/describe), retrieval (search), and flexible querying (SQL) cover the read-only domain well. Minor gap: no direct fetch-by-record identifier, though query_dataville can serve as a workaround.