Skip to main content
Glama

OSIR Domain Registrar

by com.osir

getTransferQuote

Read-onlyIdempotent

getTransferQuote: Get a transfer price quote for a domain. Requires authentication. Returns transfer price, currency, extension years, and new expiration date. Call before initiateTransfer to show the user the cost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesFully qualified domain name to quote, e.g. 'example.com'.
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
domainNo
messageNo
successNo
currencyNo
transferPriceNo
extensionYearsNo
newExpirationDateNo

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 to quote, e.g. 'example.com'."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "currency": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "extensionYears": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "newExpirationDate": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "transferPrice": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already communicate read-only, non-destructive, and idempotent behavior. The description adds the authentication requirement and what the call returns, plus the workflow cue that this is a preflight quote before a mutating transfer operation. No contradiction with 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?

Three short sentences, each earning its place: the tool's purpose, its authentication and return behavior, and the exact workflow placement. It is front-loaded with the core action and avoids redundancy with the schema.

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 simple quote tool with one required parameter and a rich output schema, this description covers what the tool does, that it requires authentication, what it returns, and when to call it. Nothing essential for correct invocation or selection is missing.

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?

Schema description coverage is 100%, so the schema fully documents 'domain' and 'sessionKey'. The description does not add parameter-level detail beyond the schema, so the baseline of 3 applies.

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+resource ('Get a transfer price quote for a domain') and clarifies that it returns transfer price, currency, extension years, and new expiration date. This sets it apart from transfer-status and pricing-list siblings by scoping it to the pre-transfer quote step.

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?

It explicitly states 'Call before initiateTransfer to show the user the cost,' giving clear contextual timing and connecting it to the relevant workflow. It does not list exclusions or compare against alternatives such as getDomainPricing or getTransferStatus, but the sequencing guidance is sufficient for selection.

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