Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
validate_ern_xmlB

Validate a finished DDEX ERN 3.8.2 NewReleaseMessage (smoke structure/order + full offline XSD). Pass xml string and/or path.

validate_package_dirA

Validate a DDEX package directory: BatchComplete filled, relative URL, DeliveryType, MD5 of message file.

explain_elementA

Explain an ERN 3.8.2 element, attribute, or concept (where it goes, spelling, related items).

element_sequenceB

Return the canonical child element order (XSD sequence / practice) for a container such as ReleaseDetailsByTerritory or SoundRecording.

list_sequencesA

List all documented ERN 3.8.2 element sequences available via element_sequence.

list_enumsB

List curated enum sets (AVS subsets + package-practice values like DeliveryType).

avs_valuesC

Return allowed values for an AVS simpleType (from vendored avs.xsd) or a curated enum id.

howto_composeA

Step-by-step guide for composing ERN 3.8.2 content (new release, vocal vs instrumental, redelivery, takedown, explicit/lyrics, preorder).

list_howtosB

List available composition howto guides.

list_elementsB

List knowledge cards available via explain_element.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
ern-382-overviewERN 3.8.2 overview
rdbt-orderReleaseDetailsByTerritory order
sdbt-orderSoundRecordingDetailsByTerritory order
batchcompleteBatchComplete package rules
common-pitfallsCommon ERN 3.8.2 pitfalls

TDQS

A3.5/5.0

Scored across 10 tools

Disambiguation4/5

Tools pair up cleanly as list_X/get_X patterns (list_sequences vs element_sequence, list_enums vs avs_values, list_elements vs explain_element), and the two validators target distinct inputs (XML string vs package directory). Minor overlap exists between list_enums and avs_values since both concern enumerated values, but descriptions clarify the boundary.

Naming Consistency4/5

Most tools follow a verb_noun convention (validate_ern_xml, list_sequences, explain_element, howto_compose). A few deviate to bare noun phrases (element_sequence, avs_values), which is mildly inconsistent but still readable and predictable within each tool family.

Tool Count5/5

Ten tools is well-scoped for a validation-plus-reference server, with each tool earning a distinct role across validation, structural reference, and composition guidance. No redundant or filler tools.

Completeness4/5

Covers validation (XML and package), schema ordering, enums, and composition howtos/element explanations, forming a coherent lifecycle for authoring and checking ERN 3.8.2. There is no tool to retrieve the raw XSD or synthesize example/valid ERN content, which would round out the surface but isn't a blocking gap.