OSIR Domain Registrar

getDomainPricing

Read-onlyIdempotent

getDomainPricing: Get pricing for domain extensions from the product catalog. Requires authentication.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`extension`	No	Domain extension to filter by, without the leading dot (e.g. 'com', 'net', 'org').
`sessionKey`	No	Session 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

Name	Required	Description	Default
`message`	No
`pricing`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 3, 2026

addedInput schema / properties / extension / description

Added value: +"Domain extension to filter by, without the leading dot (e.g. 'com', 'net', 'org')."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "pricing": {
+      "items": {
+        "properties": {
+          "currency": {
+            "type": "string"
+          },
+          "operation": {
+            "type": "string"
+          },
+          "price1Year": {
+            "type": "string"
+          },
+          "price2Year": {
+            "type": "string"
+          },
+          "price3Year": {
+            "type": "string"
+          },
+          "tld": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedSep 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only nature is covered. The description adds 'Requires authentication,' which is a useful operational precondition not expressed in annotations. No contradiction with 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?

Two short sentences front-load the purpose and follow with the authentication precondition. There is minor redundancy in repeating the tool name as a prefix, but otherwise every word earns its place.

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, fully documented optional parameters, and annotations covering the safety profile, the description is largely complete for a simple catalog lookup. It could additionally note the optional-extension behavior or differentiate from getProductCatalog, but nothing critical is missing for correct invocation.

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%, with both parameters clearly explained: 'extension' includes the no-leading-dot format and 'sessionKey' clarifies the two auth flows. The description adds no parameter-level detail, but none is needed because the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the exact resource ('pricing for domain extensions') and source ('product catalog'), making clear this is a catalog lookup rather than an availability check or registration action. It does not explicitly contrast with siblings like getProductCatalog, but the specificity is sufficient to disambiguate.

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

Usage Guidelines3/5

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

The description implies the tool is for retrieving domain-extension pricing and states the authentication precondition. However, it gives no explicit guidance about when to prefer this over alternatives such as getProductCatalog or getDomainExtensions, nor any when-not-to-use guidance.

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.