Skip to main content
Glama

OSIR Domain Registrar

by com.osir

createDnsRecord

createDnsRecord: Create a new DNS record for a domain. Requires authentication. For newly registered domains the zone is initialized automatically if missing. Returns the created record including its id for later updates or deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttlNoTime to live in seconds; defaults to 3600 when omitted.
nameYesRecord name relative to the zone, e.g. 'www', 'mail', or '@' for the apex.
typeYesRecord type: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA.
domainYesFully qualified domain name the record belongs to, e.g. 'example.com'.
contentYesRecord value, e.g. an IPv4 dotted-quad or IPv6 address for A/AAAA, a hostname for CNAME/MX/NS, or text for TXT.
priorityNoPriority for MX/SRV records only; defaults to 0 when omitted.
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.

Schema Changelog

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

  1. Changed6 schema fields changed
    • addedInput schema / properties / content / description
      Added value: +"Record value, e.g. an IPv4 dotted-quad or IPv6 address for A/AAAA, a hostname for CNAME/MX/NS, or text for TXT."
    • addedInput schema / properties / domain / description
      Added value: +"Fully qualified domain name the record belongs to, e.g. 'example.com'."
    • addedInput schema / properties / name / description
      Added value: +"Record name relative to the zone, e.g. 'www', 'mail', or '@' for the apex."
    • addedInput schema / properties / priority / description
      Added value: +"Priority for MX/SRV records only; defaults to 0 when omitted."
    • addedInput schema / properties / ttl / description
      Added value: +"Time to live in seconds; defaults to 3600 when omitted."
    • addedInput schema / properties / type / description
      Added value: +"Record type: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false), the description discloses that authentication is required, that missing zones for newly registered domains are automatically initialized, and that the created record (with id) is returned. It does not cover duplicate-name behavior or propagation timing, but the key side effects of creation and return value are transparent.

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

Conciseness4/5

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

The description is compact and front-loaded with the core action. The only redundancy is the leading 'createDnsRecord:' prefix that repeats the tool name; otherwise every sentence conveys useful information (auth, auto-initialization, return value).

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 7-parameter mutation tool with no output schema, the description covers the essential prerequisites, a notable automatic behavior, and the shape of the return value. It does not describe possible error conditions or edge cases, but the schema and sibling context fill most of what an agent needs to select and invoke the tool correctly.

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

Parameters3/5

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

The input schema already describes all seven parameters at 100% coverage, so the baseline is 3. The description adds no additional parameter-level detail, only mentioning that the returned record contains an id. No compensation is needed, but none is provided beyond the 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?

States a specific verb and resource: 'Create a new DNS record for a domain.' This clearly differentiates from sibling tools like updateDnsRecord, deleteDnsRecord, getDnsRecord, and listDnsRecords. The mention of 'new' and 'for a domain' leaves no ambiguity about the operation's scope.

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?

Provides clear context by stating authentication is required and explaining that zones are auto-initialized for newly registered domains, which signals when initializeDnsZone is unnecessary. It also mentions returning the id for later updates or deletion, pointing users to the appropriate sibling tools. However, it does not explicitly state when not to use this tool versus those alternatives.

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