OSIR Domain Registrar

createAccount

Idempotent

createAccount: Create a new OSIR customer account; step 1 of onboarding, no authentication required. The contact must be the PRINCIPAL's real ICANN registrant contact (the human or business the account is for), never the AI agent itself. Sends a verification email; complete via verifyAccount with the emailed code. While PENDING_VERIFICATION the account can search, quote and fund; billable actions need ACTIVE. Calling again for a PENDING account re-sends the verification email.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	Account login email; valid mailbox that receives the verification code.
`contact`	Yes	The principal's real ICANN registrant contact (firstName, lastName, email, phone, street1, city, country), never the AI agent itself.
`password`	No	Optional account password; if omitted the account is agent-managed until a password is set.
`agentName`	No	Name of the AI agent acting for the principal, recorded for the audit trail.
`accountType`	Yes	Account type: INDIVIDUAL or ORGANIZATION.
`agentVendor`	No	Vendor of the AI agent acting for the principal, recorded for the audit trail.
`termsVersion`	Yes	Version of the OSIR terms the principal accepted, e.g. '2026-09'.
`acceptedTerms`	Yes	Must be true; requires the principal's actual consent to the OSIR terms of service.
`principalReference`	No	Principal's own reference identifying who the agent acted for, recorded for the audit trail.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`accountId`	No
`contactId`	No
`nextSteps`	No
`verification`	No

Schema Changelog

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

Changed10 schema fields changedSep 3, 2026

addedInput schema / properties / acceptedTerms / description

Added value: +"Must be true; requires the principal's actual consent to the OSIR terms of service."

addedInput schema / properties / accountType / description

Added value: +"Account type: INDIVIDUAL or ORGANIZATION."

addedInput schema / properties / agentName / description

Added value: +"Name of the AI agent acting for the principal, recorded for the audit trail."

addedInput schema / properties / agentVendor / description

Added value: +"Vendor of the AI agent acting for the principal, recorded for the audit trail."

addedInput schema / properties / contact / description

Added value: +"The principal's real ICANN registrant contact (firstName, lastName, email, phone, street1, city, country), never the AI agent itself."

addedInput schema / properties / email / description

Added value: +"Account login email; valid mailbox that receives the verification code."

addedInput schema / properties / password / description

Added value: +"Optional account password; if omitted the account is agent-managed until a password is set."

addedInput schema / properties / principalReference / description

Added value: +"Principal's own reference identifying who the agent acted for, recorded for the audit trail."

addedInput schema / properties / termsVersion / description

Added value: +"Version of the OSIR terms the principal accepted, e.g. '2026-09'."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accountId": {
+      "type": "string"
+    },
+    "contactId": {
+      "type": "string"
+    },
+    "nextSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    },
+    "verification": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (mutation, idempotent, non-destructive), the description discloses that the call requires no auth, sends a verification email, leaves the account in PENDING_VERIFICATION with specific permitted actions, and re-sends the email if called again. These are behavioral traits not present in the schema or annotations.

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 prose is front-loaded with the core action, then gives the identity constraint, verification step, state implications, and repeat-call behavior in compact clauses. No filler sentences; each clause earns its place even though the description runs longer than the minimal example.

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?

For a 9-parameter mutation with a nested object and output schema, the description is sufficient: it covers auth requirements, step sequencing, state restrictions, and repeated call behavior. Output details are delegated to the output schema, which is appropriate.

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?

All nine inputs are documented in the schema (100% coverage), so the baseline is met. The description reinforces the contact-principal rule, but that rule largely repeats the schema's contact description and does not add new parameter semantics.

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 opens with a concrete verb and resource—'Create a new OSIR customer account'—and adds workflow context ('step 1 of onboarding, no authentication required'). It is distinguishable from siblings like createContact and verifyAccount because it defines the account-level creation step and even names verifyAccount as the follow-up.

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?

'Step 1 of onboarding' plus 'complete via verifyAccount' gives a clear invocation context, and the PENDING_VERIFICATION vs ACTIVE states explain when the account is usable. It does not list exclusions or alternative tools for non-account cases, but the workflow context is unambiguous.

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 tools Inspect

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.

createAccount

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources