Skip to main content
Glama

Create or update a nameserver profile

eurodns_nameserver_save_profile

Create or update a nameserver profile. When updating, fetch the existing profile first, as omitted fields are cleared. Changing a profile affects all domains using it.

Instructions

Creates a nameserver profile from body when id is omitted, or updates the profile with that id, and returns the saved profile. An update must carry every field and every nameserver you keep, because the API clears anything omitted: start from eurodns_nameserver_get_profile rather than from the changed servers alone. Changing a profile changes the delegation of every domain pointing at it, so read it first instead of guessing what it holds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the profile to update, from eurodns_nameserver_get_profile. Omit it to create a new profile.
bodyYesThe profile: a name and its nameservers, each with an fqdn and, for glue records, ipV4Address and ipV6Address. When updating, send every field and every nameserver you keep: the API clears anything omitted.
langNoTwo-letter language code for the messages the API returns, e.g. en. Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResponse body as returned by the API.
statusYesUpstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A3.9/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description warns that the API clears any omitted nameservers and that changing a profile affects delegation for all domain pointing at it. This is destructive behavior, but the annotations declare destructiveHint: false, creating a direct contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well structured: purpose first, then critical update behavior, then side-effect warning. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the nested nameserver structure and create/update semantics, the description covers what the tool does, how to construct an update, and an important side effect. It also states the return value is the saved profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the body shape, nameservers with fqdn and glue-record IPs, and the update-clearing behavior. It does not explain canDelete or defaultProfile, but overall adds meaningful parameter semantics beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates or updates a nameserver profile and returns the saved profile. It names the resource and the create/update behavior, making it easy to distinguish from related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete guidance for updates: start from eurodns_nameserver_get_profile and send every field you keep. It does not explicitly enumerate alternatives for creation, but the create/update distinction is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.