Popdot AI

get_price_quote

Read-only

Get a price quote for renting a specific domain for a given duration. Returns the computed rental cost, tier info, and pricing breakdown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domainId`	Yes	The domain to price: its id from search_domains, or its name (for example addedtocart.shop)
`duration`	Yes	ISO 8601 duration: PT1H (1 hour), PT4H (4 hours), P1D (1 day), P7D (1 week), P30D (30 days)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	No
`hours`	No
`feeNote`	No
`currency`	Yes
`domainId`	Yes
`duration`	No
`available`	No
`tierScore`	No
`totalCost`	Yes
`fullDomain`	No
`serviceFee`	No
`ownerPayout`	No
`priceSource`	No
`rentalPrice`	No
`durationLabel`	No
`priceBreakdown`	No
`ownerCommission`	No
`ownerCommissionPercent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / properties / domainId / description

Previous value: -"The unique ID of the domain to price"New value: +"The domain to price: its id from search_domains, or its name (for example addedtocart.shop)"

Changed2 schema fields changedAug 27, 2026
- addedOutput schema / properties / ownerCommission
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / ownerCommissionPercent
```
Added value: +{
+  "type": "number"
+}
```

Changed1 schema field changedAug 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "available": {
+      "type": "boolean"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "domainId": {
+      "type": "string"
+    },
+    "duration": {
+      "type": "string"
+    },
+    "durationLabel": {
+      "type": "string"
+    },
+    "feeNote": {
+      "type": "string"
+    },
+    "fullDomain": {
+      "type": "string"
+    },
+    "hours": {
+      "type": "number"
+    },
+    "ownerPayout": {
+      "type": "number"
+    },
+    "priceBreakdown": {
+      "properties": {
+        "daily": {
+          "type": "number"
+        },
+        "hourly": {
+          "type": "number"
+        },
+        "monthly": {
+          "type": "number"
+        },
+        "weekly": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "priceSource": {
+      "enum": [
+        "owner",
+        "algorithm"
+      ],
+      "type": "string"
+    },
+    "rentalPrice": {
+      "type": "number"
+    },
+    "serviceFee": {
+      "type": "number"
+    },
+    "tier": {
+      "type": "string"
+    },
+    "tierScore": {
+      "type": "number"
+    },
+    "totalCost": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "domainId",
+    "totalCost",
+    "currency"
+  ],
+  "type": "object"
+}

First observedJul 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to restate safety. It adds useful behavioral detail about the return (rental cost, tier info, pricing breakdown) beyond the schema. It does not cover quote expiry or price variability, but openWorldHint covers external changes.

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?

A single, front-loaded sentence that clearly names the action and result. Every clause adds value with no filler or redundancy.

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?

For a read-only price-quote tool, the description, schema, and annotations together cover purpose, inputs, and output. It could mention that quotes may become stale, but that is already implied by openWorldHint, making this adequate.

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 both domainId and duration are fully documented with formats and examples. The description adds no parameter-specific meaning, so the baseline 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 states a specific verb (get), resource (price quote), and scope (renting a specific domain for a duration). It clearly distinguishes itself from siblings like rent_domain (actual rental) and search_domains (finding domains) without requiring schema inspection.

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 phrase 'for renting a specific domain' implies this tool is a pre-rental pricing step, but it never names an alternative or states when not to use it. No explicit comparison with sibling tools like rent_domain or check_availability, leaving the workflow to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Popdot AI 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.