sdccdif
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --host | No | Catalog host fixed at server start. No tool takes a URL; the catalog host is set with --host. | |
| --contact-name | No | Overrides the publisher contact point name from the declared default. | |
| --contact-email | No | Overrides the publisher contact point email from the declared default; an empty address omits the contact point. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Describe published Semantic Data Charter models in CDIF terms. write_cdif takes a model identifier (ct_id), fetched from https://sdcstudio.axius-sdc.com, or package directories on disk, and returns the CDIF JSON-LD document under document. Read-only apart from the document it returns; no account; no tool takes a URL.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| write_cdifB | Write the CODATA CDIF description (JSON-LD: Discovery, Data Description with every variable, Codelists, and the sentinel domain for the sixteen exceptional values) of one published Semantic Data Charter model. The document cites the model's schema by URL and SHA-256. Validated in this package's CI with CDIF's own framing, JSON Schema and SHACL checks from a pinned snapshot. |
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 1 tool
With only one tool there is no sibling overlap, so an agent cannot misselect between tools. However, the single name does not signal whether the operation is a create-only or full write/replace, leaving mild ambiguity about side effects.
write_cdif follows a clean verb_noun snake_case pattern, matching common MCP conventions. The sample size is one, and the 'cdif' abbreviation is opaque relative to the server name 'sdccdif'.
A single tool is too thin for a server that otherwise implies a workflow (write plus validate, retrieve, or list CDIF documents). The one tool is substantive but leaves the surface feeling under-scoped.
Only the write operation exists; there is no way to read, list, validate, or update an existing CDIF description despite validation being central to the description. Agents hit a dead end after writing and cannot inspect or verify output.