Skip to main content
Glama

OSIR Domain Registrar

by com.osir

osirSitePublish

Publish a single-page website to a live HTTPS URL on Osir (free tier) — ANY complete HTML document works: the user's own site, a page designed in this chat, or one from the osirSiteDesignBrief flow. Required: name (lowercase letters/digits/hyphens, e.g. 'bar-mediterran'), html (complete document, max 1 MiB). Calling again with the same name redeploys the new version. Optional: region ('us'|'al'); designContract (true ONLY for pages generated via the osirSiteDesignBrief flow — additionally enforces its output contract: exactly one , self-contained, no external scripts/CSS except Google Fonts, no iframes; never set it for a user's own site). For MULTI-FILE sites (separate CSS/JS/images) use osirAppCreateUpload + osirAppDeploy with a zip instead. Then poll osirAppStatus until READY. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlYes
nameYes
regionNo
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.
designContractNo

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it reveals redeployment behavior ('Calling again with the same name redeploys the new version'), size limits ('max 1 MiB'), naming constraints, designContract enforcement rules, and the authentication requirement. This gives an agent a realistic picture of side effects and prerequisites.

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 long but every clause earns its place: core purpose is front-loaded, required versus optional parameters are clearly separated, and the sibling-tool alternative is placed logically at the end. No filler or redundant restatement of the tool name.

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 lack of annotations and output schema, the description is remarkably complete: it covers all parameters, required inputs, authentication, constraints, redeploy semantics, and the exact alternative path for multi-file sites. An agent has everything needed to decide whether and how to invoke this tool correctly.

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

Parameters5/5

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

Schema description coverage is only 20%, so the description must compensate, and it does: it details the name format with an example, mandates a complete <html> document with a size cap, enumerates region options, and explains the meaning and restricted usage of designContract. This adds substantial semantic value beyond the bare 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 states a specific action and resource: 'Publish a single-page website to a live HTTPS URL on Osir (free tier)'. It clarifies what inputs are acceptable ('ANY complete HTML document works') and distinguishes itself from multi-file deployment flows by naming sibling tools.

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

Usage Guidelines5/5

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

It explicitly explains when to use this tool (single-page complete HTML documents) and when not to ('For MULTI-FILE sites... use osirAppCreateUpload + osirAppDeploy with a zip instead'), including follow-up polling via osirAppStatus. It also gives a clear conditional rule for designContract, saying it is only for osirSiteDesignBrief-generated pages.

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

B3.1/5.0
Disambiguation2/5

The set has several near-duplicate or heavily overlapping tools: initiateTransfer and transferDomain appear to do the same thing, and generateDomainSuggestions, bulkDomainSuggestions, suggestAlternatives, spinDomainWords, and addPrefix/addSuffixToDomain all occupy suggestion space. Account/profile tools like getAccountSummary, getMyProfile, getRecentActivity, and getMyAuditLogs also blur together.

Naming Consistency2/5

Many tools follow verb_noun camelCase (createDnsRecord, listInvoices, updateContact), but the broader set mixes styles: osirAppCreateUpload vs osirAppList vs osirAppStatus, plus inconsistent verbs like check/verify/validate/preview for similar lookup actions. The naming is readable but not predictable across the full surface.

Tool Count1/5

105 tools is an extreme count for any single MCP server, even one spanning domain registration, DNS, VPS, email, billing, app deployment, and site publishing. The surface would be far more coherent split into focused servers by domain.

Completeness3/5

Core domain, DNS, billing, VPS, mail, and app deployment workflows are broadly covered. However, there are notable gaps: no way to update or reassign the contacts on an existing domain, no update operation for host/glue records, and no VPS power operations like reboot or stop outside the external control panel.

Resources