Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOMENESHOP_DEBUGNoSet to true to log every API request to stderr
DOMENESHOP_TOOLSNoComma-separated allowlist of tool names to expose
DOMENESHOP_API_TOKENYesAPI token from the Domeneshop control panel
DOMENESHOP_READ_ONLYNoSet to true to expose only read-only tools
DOMENESHOP_API_SECRETYesThe matching API secret
DOMENESHOP_TIMEOUT_MSNoPer-request timeout in milliseconds30000
DOMENESHOP_DISABLED_TOOLSNoComma-separated tool names to hide

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Tools for a Domeneshop (domeneshop.no) account: domains, DNS records, HTTP forwards, dynamic DNS and invoices. Domain-scoped tools take a numeric domain_id: look it up with list_domains first, and DNS record IDs with list_dns_records. To change part of a DNS record use patch_dns_record; update_dns_record replaces the whole record and drops omitted fields. upsert_dns_record sets the single record for a host and type, creating it if needed. TTL values are in seconds (60-604800, a multiple of 60). Use '@' as host for the domain root. Write tools change live DNS; confirm the intended change with the user before deleting or overwriting records.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_domainsA

List all domains on the Domeneshop account, optionally filtered by domain name. Use this first to find the domain_id the other tools need.

get_domainA

Get details for a single domain by its Domeneshop domain ID: expiry, renewal, nameservers and active services.

list_dns_recordsB

List DNS records for a domain, optionally filtered by host and/or record type.

get_dns_recordB

Get a single DNS record by ID.

create_dns_recordB

Create a new DNS record for a domain. Returns the stored record, including its new ID.

update_dns_recordA

Replace an existing DNS record. This overwrites the whole record, so send every field it should keep: any omitted field is dropped, and leaving out ttl resets it to the default 3600 seconds. To change only some fields, use patch_dns_record instead. Returns the stored record.

patch_dns_recordA

Change only some fields of an existing DNS record, e.g. just data or ttl. The current record is read first and every field you leave out keeps its stored value; when you change the type, give the new type's required fields too. Prefer this over update_dns_record. Returns the stored record.

upsert_dns_recordA

Make sure a host has exactly this record of the given type: updates the existing record for that host and type, or creates one if there is none. When updating, optional fields you leave out (e.g. ttl, priority) keep their stored value. Fails without changing anything if the host already has several records of that type (common for MX and TXT); then use patch_dns_record with a record_id, or create_dns_record to add another. Returns { action: "created" | "updated", record }.

delete_dns_recordB

Delete a DNS record. This cannot be undone.

list_forwardsA

List all HTTP forwards configured for a domain.

get_forwardB

Get the HTTP forward configured for a specific host.

create_forwardA

Create a new HTTP forward for a domain. Fails if the host already has a forward or a conflicting A, AAAA, ANAME or CNAME record.

update_forwardA

Update an existing HTTP forward for a domain. Returns the stored forward. frame keeps its stored value unless given. The host itself cannot be changed: to move a forward, delete it and create it again for the new host.

delete_forwardB

Delete an HTTP forward. This cannot be undone.

update_dyndnsA

Point one or more hostnames at the given (or the caller's apparent) IP address using Domeneshop's dynamic DNS protocol. The record type (A or AAAA) follows from the address; a missing record is created, an existing one overwritten.

list_invoicesA

List invoices from the past three years on the Domeneshop account, optionally filtered by status.

get_invoiceA

Get details for a single invoice, including a link to the PDF.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 17 tools

Disambiguation4/5

Resources are cleanly partitioned (domains, DNS records, HTTP forwards, invoices) and the four DNS write tools (create/update/patch/upsert) are explicitly differentiated, including a cross-reference telling the agent to prefer patch_dns_record. The only residual risk is that update/upsert/patch all mutate a record and an agent could pick wrong, but the descriptions genuinely resolve this.

Naming Consistency5/5

Every tool follows the same snake_case verb_noun pattern (list_domains, get_dns_record, create_forward, patch_dns_record, update_dyndns). The verb set is small and applied predictably across all four sub-resources.

Tool Count4/5

17 tools across four sub-domains (2 domain, 7 DNS, 5 forward, 2 invoice) is proportionally balanced and each tool covers a distinct operation. It sits just outside the ideal 3-15 band and the four DNS mutation tools add some redundancy.

Completeness4/5

DNS records and HTTP forwards both have full CRUD plus partial-update and upsert, and domains/invoices are readable with useful filters. Gaps are minor and likely intentional: no domain settings/nameserver update or domain deletion, and invoices are read-only, but the core workflows are all reachable.

Maintenance

ActivityActive
ResponsivenessNo recent community issues