Skip to main content
Glama
cldf-mcp

cldf-mcp

by hsouf

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLDF_MCP_CONFIGNoPath to extra TOML to add or override datasets (experimental, --config).
CLDF_MCP_DATA_DIRNoDirectory where the pinned datasets are downloaded and the local SQLite database is built (--data-dir).~/.cache/cldf-mcp (Linux), ~/Library/Caches/cldf-mcp (macOS), %LOCALAPPDATA%\cldf-mcp (Windows)

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_datasetsA

List the loaded datasets with their release versions, coverage, licenses and how to cite them.

find_languageA

Find languages by name or code. Returns Glottocodes, family, macroarea and which dataset entries have data.

Use this before other tools when a name might be ambiguous (e.g. 'Arabic' is a family; WALS has Arabic varieties). Candidates are ranked: exact codes, exact names, alternate names, then partial matches.

search_featuresA

Search typological features by keyword. Returns feature IDs, names, possible values and how many languages are coded for each.

get_featureA

Describe one feature: definition, chapter and authors, and how its values are distributed, counted by languages, families and genera.

get_valuesA

Look up specific datapoints: the value of each feature for each language, with sources, comments and full citations. Unresolvable names are reported in 'errors' with candidates instead of failing the call.

When several dataset entries share a Glottocode (e.g. Basque and Basque dialects), the main entry is used and the others are listed; pass a dataset ref like 'wals:bso' to pick a specific one.

language_profileA

Everything known about one language: Glottolog identity, classification, endangerment and description status, plus all its feature values per dataset.

filter_languagesA

Find languages matching feature conditions, e.g. SOV order AND postpositions.

Returns match counts against the number of languages coded for all conditions (the denominator), with family and genus counts and the families contributing most matches, plus the matching languages.

crosstabA

Cross-tabulate two features over the languages coded for both. Each cell gives languages, families and genera attesting the combination and the share of its largest family, so you can tell a cross-linguistic tendency from the signature of one big family. Use this to check implicational universals.

classificationB

Glottolog classification of a language or group: lineage, children (with how many dataset entries fall under each), sisters, and the number of languages below.

get_sourceA

Full bibliographic references for source IDs cited in datapoints.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
typology-caveatsSampling bias, family counts, coverage and citation: read before generalising from counts.
datasetsVersions, licenses and citations of the loaded datasets.

TDQS

A3.6/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct roles: find_language (name lookup), search_features (keyword search), get_feature (single feature detail), get_values (datapoint lookup), filter_languages (conditional query), crosstab (two-feature tabulation), classification (hierarchy), get_source (citations). There is some overlap between search_features/get_feature and between get_values/language_profile, but the descriptions clarify that the latter pairs operate at different granularities.

Naming Consistency3/5

Seven tools follow a verb_noun pattern (list_datasets, find_language, search_features, get_feature, get_values, filter_languages, get_source), but three use bare noun names (language_profile, crosstab, classification). The conventions are mixed but still readable and semantically clear.

Tool Count5/5

Ten tools is well-scoped for a typological-database explorer, with each tool covering a distinct query angle (discovery, lookup, filtering, aggregation, classification, sources). No tool feels redundant or padded.

Completeness4/5

The surface covers discovery (datasets, languages, features), retrieval (values, profiles, sources), and analysis (filtering, crosstab, classification), which is strong for a read-only typology server. Minor gaps exist, such as no direct export/aggregate-statistics tool, but core workflows are fully supported.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues