Skip to main content
Glama

OSIR Domain Registrar

by com.osir

updateNameservers

updateNameservers: Update nameservers for a domain. Replaces the current nameserver set with the given list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesFully qualified domain name, like "example.com", without scheme.
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.
nameserversYesList of nameserver hostnames, e.g. ["ns1.example.com", "ns2.example.com"].

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Fully qualified domain name, like \"example.com\", without scheme."
    • addedInput schema / properties / nameservers / description
      Added value: +"List of nameserver hostnames, e.g. [\"ns1.example.com\", \"ns2.example.com\"]."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses a key behavioral trait beyond the annotations: the operation replaces the entire current nameserver set rather than adding to it. This is important side-effect information for an agent. The annotations already cover read-only and destructive hints, so the description's additional replacement detail earns a solid score.

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 two sentences with no filler. The verb and resource are front-loaded, and the critical replacement behavior is stated immediately after. Every word earns its place.

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

Completeness4/5

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

For a straightforward mutation tool with a fully documented schema and annotations, the description is largely complete. It would benefit from a brief note on prerequisites or a pointer to related tools like updateDnsRecord, but nothing essential is missing for correct invocation.

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 input schema already documents all three parameters with good coverage, so the baseline is 3. The description adds real value above the schema by clarifying the nameservers parameter is not additive—it replaces the existing set. This prevents a common misinterpretation.

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

Purpose4/5

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

The description clearly identifies the operation: 'Update nameservers for a domain' and adds specificity with 'Replaces the current nameserver set with the given list.' It is not a tautology, and it conveys the exact resource and behavior. However, it does not explicitly differentiate itself from sibling tools like updateDnsRecord, where confusion could arise between domain nameservers and DNS records.

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?

The context is clear: use this when you need to update the nameserver set for a domain. The replacement semantics further clarify the intended use. However, there are no explicit exclusions or comparisons to alternatives such as updateDnsRecord, which could help an agent decide between these related operations.

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

All OSIR Domain Registrar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most tools target distinct resource-action pairs, but there are several overlapping clusters: six domain-suggestion tools (addPrefixToDomain, addSuffixToDomain, generateDomainSuggestions, bulkDomainSuggestions, spinDomainWords, suggestAlternatives) and overlapping account-info tools (getMyProfile, getAccountSummary, getRecentActivity, getMyAuditLogs). Descriptions help, but with 105 tools an agent will regularly face near-identical choices.

Naming Consistency4/5

The dominant convention is verbNoun camelCase (createContact, listDnsRecords, updateNameservers), which is readable and predictable. Deviations exist in the osirApp* and osirSite* families, where the noun precedes the verb, and a few names like suggestAlternatives and spinDomainWords break the pattern.

Tool Count1/5

105 tools is far beyond a coherent MCP server surface; even if the platform genuinely spans domains, DNS, email, VPS, billing, and app hosting, this should be split into focused servers. Many tools are single-purpose getters that add selection overhead rather than earning their place as one integrated set.

Completeness4/5

The covered services have broad CRUD/lifecycle coverage: contacts, DNS, hosts, domains, email, VPS, SSH keys, invoices, and Osir apps all have create/read/update/delete paths. Some registrar-specific operations (e.g., contact reassignment after registration, domain deletion/redemption) are missing, and the sheer sprawl makes coverage hard to verify.

Resources