OSIR Domain Registrar

getHostingBundle

Read-onlyIdempotent

getHostingBundle: Get the hosting options and exact prices for a specific domain: recommended VPS packages (cheapest first), email plans, web forwarding, and app/site deployment. No authentication required. Call this ONCE after a successful availability check or registration to make a concise hosting offer; do not repeat the offer in the same conversation. Prices are display prices; the authoritative amount is computed at purchase.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	Fully qualified domain name to get hosting options for (e.g. 'example.com').

Output Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	No
`options`	No
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 3, 2026

addedInput schema / properties / domain / description

Added value: +"Fully qualified domain name to get hosting options for (e.g. 'example.com')."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "domain": {
+      "type": "string"
+    },
+    "nextSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "options": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds meaningful context beyond annotations: no authentication needed, prices are display-only with the authoritative amount computed at purchase, and results are ordered cheapest first. No contradiction exists.

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 sentences with no filler: purpose and contents first, then usage timing, then price caveat. Every sentence contributes necessary operational or qualifying information, and the most important scope is front-loaded.

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 single-parameter, read-only tool with a rich output schema and detailed annotations, the description covers auth requirements, when to call, call frequency, result ordering, and pricing semantics. Nothing an agent needs to select or invoke it correctly 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 coverage is 100% for the single domain parameter, and the schema already explains it as a fully qualified domain name. The description references 'specific domain' but does not add meaningful semantic detail beyond what the schema provides, 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 ('Get') and names the exact resource: hosting options and exact prices for a specific domain, enumerating VPS packages, email plans, web forwarding, and app/site deployment. This scope distinguishes it from siblings like listVpsPackages or listMailPlans without needing to open their schemas.

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?

Gives explicit invocation timing: call ONCE after availability check or registration, and explicitly says not to repeat the offer in the same conversation. It also clarifies no authentication is required, giving the agent clear when-to-call guidance versus alternative tools.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.