Skip to main content
Glama

OSIR Domain Registrar

by com.osir

getMailboxQuote

Read-onlyIdempotent

getMailboxQuote: Get a display-only price quote for a mailbox plan. The backend re-derives the authoritative price at purchase. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNoPayment term: 'MONTHLY' or 'ANNUAL' (default ANNUAL).
packageIdYesMailbox plan id from listMailPlans.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNo
messageNo
successNo
currencyNo
packageIdNo
priceCentsNo
quotaBytesNo
packageNameNo

Schema Changelog

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

  1. Changed3 schema fields changed
    • addedInput schema / properties / packageId / description
      Added value: +"Mailbox plan id from listMailPlans."
    • addedInput schema / properties / term / description
      Added value: +"Payment term: 'MONTHLY' or 'ANNUAL' (default ANNUAL)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "currency": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "packageId": {
+      "type": "string"
+    },
+    "packageName": {
+      "type": "string"
+    },
+    "priceCents": {
+      "type": "integer"
+    },
+    "quotaBytes": {
+      "type": "integer"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "term": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond that: the quote is display-only, not authoritative, and requires authentication. This gives the agent useful behavioral expectations without contradicting the annotations.

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 key purpose. The additional sentences about authoritative price and authentication are relevant and non-redundant. Minor deduction for repeating the tool name at the start.

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?

Given the output schema exists and annotations cover safety, the description sufficiently covers purpose, auth requirements, and non-authoritative behavior. It is complete enough for an agent to call the tool correctly, though it could optionally mention that listMailPlans provides valid package IDs.

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?

Input schema coverage is 100%, with each parameter already documented, including term default and packageId source. The description does not add parameter-level meaning, but the schema carries the full burden, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Get a display-only price quote for a mailbox plan.' It clearly distinguishes this from other tools like getTransferQuote by scoping it to mailbox plans. The display-only qualifier also clarifies the nature of the result.

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 description conveys clear context: this tool is for display-only quoting, requires authentication, and the backend re-derives the authoritative price at purchase. It implies the tool is for pre-purchase previews and not for final pricing, though it does not explicitly name alternative tools or when-not-to-use conditions.

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