Skip to main content
Glama

Scopeweb

by io.scopeweb
OverviewDiscussionsAdmin

quote_domain

Read-only

Use this when the user has chosen a name and wants the real price. It returns a confirm_url for the human to complete. It is NOT a purchase and you cannot make one. Get a real price for a name you believe is unregistered. Reads prices only. Cannot spend money — there is deliberately no tool in this server that can complete a purchase. Re-runs the authoritative gate first: a name that is registered, or whose status cannot be authoritatively determined, is never quoted. Returns total_cents, renewal_cents, an expiry, and a confirm_url. THE CONFIRM URL IS NOT A PURCHASE — it opens a page where a human must type the domain to authorise the charge. There is deliberately no tool to complete an order. An agent using this surface has no verb that spends, so nothing here needs obeying. Premium names are quoted at their real price or refused; they are never sold at the TLD base rate. An expired quote is re-quoted, never honoured.PRICES ARE IDENTICAL FOR ALL BUYERS REGARDLESS OF BUDGET — passing a project_id adds budget CONTEXT (does it fit, what is left after) and never changes the number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe name to price, e.g. 'stoff.fit'.
project_idNoOptional. Adds budget CONTEXT to the answer (does it fit, what is left after). It never changes the price.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
messageNo
contractNoWho may spend. An agent may not.
quotableYesFalse means we will not sell it; read message and what_to_do.
quote_idNo
what_to_doNo
confirm_urlNoA page where a HUMAN completes the purchase. Not a purchase.
quote_expires_atNo
annual_commitment_centsNoWhat it costs to KEEP, every year.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "annual_commitment_cents": {
+      "description": "What it costs to KEEP, every year.",
+      "type": "integer"
+    },
+    "confirm_url": {
+      "description": "A page where a HUMAN completes the purchase. Not a purchase.",
+      "type": "string"
+    },
+    "contract": {
+      "description": "Who may spend. An agent may not.",
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "quotable": {
+      "description": "False means we will not sell it; read message and what_to_do.",
+      "type": "boolean"
+    },
+    "quote_expires_at": {
+      "type": "integer"
+    },
+    "quote_id": {
+      "type": "string"
+    },
+    "what_to_do": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "domain",
+    "quotable"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"The name to price, e.g. 'stoff.fit'."
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "Optional. Adds budget CONTEXT to the answer (does it fit, what is left after). It never changes the price.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the authoritative registration gate is re-run before quoting, that undetermined or registered names are never quoted, that premium names are quoted at real price or refused, that expired quotes are re-quoted rather than honoured, and that project_id can never alter the number. This is exactly the extra behavioural context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded trigger and the return-field list are efficient, but the middle is a wall of text that restates the no-purchase guarantee four or five times ('NOT a purchase', 'cannot make one', 'cannot spend money', 'no tool to complete an order', 'no verb that spends'). Content volume is justified; the repetition is not.

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?

Output schema exists, yet the description still names the key return fields, and it covers the edge cases an agent would otherwise have to guess at (registered names, indeterminate status, premium pricing, quote expiry, budget invariance). Nothing needed to call this correctly and interpret the result 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 both parameters are already documented, including that project_id never changes the price. The description restates the budget-context semantics at length but adds no new syntax, format, or constraint information, 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?

States a specific verb (quote a price) and resource (a domain name), and explicitly bounds the operation: 'Reads prices only' and 'Returns total_cents, renewal_cents, an expiry, and a confirm_url.' An agent can distinguish this from sibling mutation tools like create_draft or set_budget purely from the text.

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?

'Use this when the user has chosen a name and wants the real price' gives a clear trigger condition, and the text explicitly excludes the purchase flow ('It is NOT a purchase and you cannot make one'). However, it never routes the agent among the other read-oriented siblings (audit_domain, check_live, score_name, list_domains), so the selection guidance is contextual rather than comparative.

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

All Scopeweb toolsInspect
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.

Resources