audit.domains - Domain Valuation

Appraise a domain name

appraise_domain

Read-onlyIdempotent

Estimate the fair value of one domain name with its low/high interval. A full cached appraisal includes its nearest recorded sales; catalog answers include only published fields. Otherwise a verified storedFigure can return the same public interval already in the report HTML, with source methodology, edition and artifact digest, but no scores, comparables or ODVS record. Use search_recorded_sales to browse sales and find_comparable_sales for just the five nearest sales. Deterministic: same name, same figure; confidence, when present, is an internal 0 to 100 score, not a probability. Without any cached, published or stored figure, returns no figure but a browser report link, 3 nearest published names for context and a next step. Cached answers, keyless catalog figures and public stored intervals use no API credits. A default-profile cache miss with an authorized write-scope paid API key (HTTP header Authorization: Bearer ad_live_...) can consume one API credit even for a catalog name, subject to allowance, rate limits and server budget. Rejected keyed runs can return an error. MCP cache hits use no API credits; without a key, catalog fallbacks are free. On the default profile a cache miss with an authorized write-scope paid key can consume one API credit even for a catalog name. Purchasing a current appraisal through an operator-funded agent account costs $0.03 per purchase (https://audit.domains/machine-account; live status, terms and protocol: GET https://audit.domains/api/machine/resolve). That is a separate paid purchase, not a charge for this MCP lookup. Fresh runs require write scope, remaining allowance and available server budget; card purchases use a hosted Square checkout.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "appraise_domain"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The one domain name to appraise, such as example.com. A pasted URL is accepted.

Output Schema

Name	Required	Description
`next`	No	Present with notAppraised: {tool, arguments} when a paid route to this name's figure is open on this server, otherwise the report link ({url}) that computes it in the reader's browser at no cost.
`citeAs`	Yes	A structured citation. Quote `text` or build your own from the fields. Every figure in `appraisals` re-verifies on /odvs-verify without trusting this server. Tools whose answer is not an appraisal (a bracket, which withholds estimates by contract, and the recorded-sales tools, whose rows are not hashed) return an empty `appraisals`. A stored interval also has no ODVS record: its artifact digest is provenance, not a standalone proof of these projected fields.
`citation`	Yes
`nextStep`	No	One line on what to do next when no figure was computed.
`purchase`	No	Present when this server sells a fresh appraisal by card: call the named tool to open a checkout for the user.
`appraisal`	No	Absent when storedFigure or notAppraised is present: no full appraisal was computed on this server for this response.
`reportUrl`	Yes
`agentTrial`	No	Present with notAppraised (Lane 04, F4): free server-side fresh appraisals this caller can still claim (remaining) and how a trial is obtained (how). 0 with operator_required means an operator-issued grant is the only route today.
`unattended`	No	Present with notAppraised: how an agent gets a fresh figure with no person at purchase time, from a balance a person prepaid and a spending grant they issued. POST request; the 402 answer lists the purchase actions.
`certificate`	No	Present with a figure while certificates are on sale: the checkout link (url) where the user buys a verifiable certificate of this appraisal, for a listing or a negotiation.
`notAppraised`	No	The name that was not computed here. Not an error: open reportUrl, where the same engine runs in the reader's browser at no cost.
`registration`	No	Present with notAppraised: whether the name is registered, from live DNS and RDAP (status registered, unregistered, likely_unregistered or unknown).
`storedFigure`	No	Only the verified value interval already public in the report HTML, read from a stored canonical-engine result when no full MCP result or catalog figure is available. No scores, comparables or ODVS record. sha256 names the stored source artifact, not a standalone proof of this projection.
`nearestCatalog`	No	Up to 3 published catalog names nearest the requested one, with their catalog figures. Context for the user, never the requested name's value.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / certificate

Added value: +{
+  "description": "Present with a figure while certificates are on sale: the checkout link (url) where the user buys a verifiable certificate of this appraisal, for a listing or a negotiation.",
+  "properties": {
+    "priceUsd": {
+      "type": "number"
+    },
+    "sku": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed6 schema fields changedOct 19, 2026

addedOutput schema / properties / agentTrial

Added value: +{
+  "description": "Present with notAppraised (Lane 04, F4): free server-side fresh appraisals this caller can still claim (remaining) and how a trial is obtained (how). 0 with operator_required means an operator-issued grant is the only route today.",
+  "properties": {
+    "how": {
+      "type": "string"
+    },
+    "remaining": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / unattended / properties / note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / unattended / properties / purchaseRequest
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / unattended / properties / recipeHash
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / unattended / properties / recipeId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / unattended / properties / recoverRequest
```
Added value: +{
+  "type": "object"
+}
```

Changed3 schema fields changedOct 15, 2026

changedOutput schema / properties / appraisal / description

Previous value: -"Absent when notAppraised is present: the name is outside the published catalog and was not computed on this server."New value: +"Absent when storedFigure or notAppraised is present: no full appraisal was computed on this server for this response."

changedOutput schema / properties / citeAs / description

Previous value: -"A structured citation. Quote `text` or build your own from the fields. Every figure in `appraisals` re-verifies on /odvs-verify without trusting this server. Tools whose answer is not an appraisal (a bracket, which withholds estimates by contract, and the recorded-sales tools, whose rows are not hashed) return an empty `appraisals`."New value: +"A structured citation. Quote `text` or build your own from the fields. Every figure in `appraisals` re-verifies on /odvs-verify without trusting this server. Tools whose answer is not an appraisal (a bracket, which withholds estimates by contract, and the recorded-sales tools, whose rows are not hashed) return an empty `appraisals`. A stored interval also has no ODVS record: its artifact digest is provenance, not a standalone proof of these projected fields."

addedOutput schema / properties / storedFigure

Added value: +{
+  "additionalProperties": false,
+  "description": "Only the verified value interval already public in the report HTML, read from a stored canonical-engine result when no full MCP result or catalog figure is available. No scores, comparables or ODVS record. sha256 names the stored source artifact, not a standalone proof of this projection.",
+  "properties": {
+    "dataEdition": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "fairUsd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "highUsd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "lowUsd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "methodologyVersion": {
+      "description": "Active methodology configuration in the memo identity; a preserved payload method stamp can differ.",
+      "type": "string"
+    },
+    "sha256": {
+      "pattern": "^[0-9a-f]{64}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "domain",
+    "fairUsd",
+    "lowUsd",
+    "highUsd",
+    "methodologyVersion",
+    "dataEdition",
+    "sha256"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 13, 2026

changedOutput schema / properties / next / description

Previous value: -"Present with notAppraised: the report link ({url}) that computes this name's figure in the reader's browser at no cost."New value: +"Present with notAppraised: {tool, arguments} when a paid route to this name's figure is open on this server, otherwise the report link ({url}) that computes it in the reader's browser at no cost."

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / next

Added value: +{
+  "description": "Present with notAppraised: the report link ({url}) that computes this name's figure in the reader's browser at no cost.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / unattended

Added value: +{
+  "description": "Present with notAppraised: how an agent gets a fresh figure with no person at purchase time, from a balance a person prepaid and a spending grant they issued. POST request; the 402 answer lists the purchase actions.",
+  "properties": {
+    "request": {
+      "type": "object"
+    },
+    "service": {
+      "type": "string"
+    },
+    "setupUrl": {
+      "type": "string"
+    },
+    "then": {
+      "type": "string"
+    },
+    "usd": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / registration

Added value: +{
+  "description": "Present with notAppraised: whether the name is registered, from live DNS and RDAP (status registered, unregistered, likely_unregistered or unknown).",
+  "type": "object"
+}

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / purchase

Added value: +{
+  "description": "Present when this server sells a fresh appraisal by card: call the named tool to open a checkout for the user.",
+  "properties": {
+    "how": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 6, 2026

changedInput schema / properties / domain / description

Previous value: -"The domain name, for example example.com. A pasted URL is accepted."New value: +"The one domain name to appraise, such as example.com. A pasted URL is accepted."

addedOutput schema / properties / nearestCatalog

Added value: +{
+  "description": "Up to 3 published catalog names nearest the requested one, with their catalog figures. Context for the user, never the requested name's value.",
+  "items": {
+    "properties": {
+      "basis": {
+        "description": "Why it was picked.",
+        "type": "string"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "fairUsd": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "domain",
+      "fairUsd",
+      "basis"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "description": "One line on what to do next when no figure was computed.",
+  "type": "string"
+}

Changed2 schema fields changedSep 30, 2026

changedOutput schema / properties / appraisal / description

Previous value: -"Absent when notAppraised is present: the name is outside the published catalog and no API key was presented."New value: +"Absent when notAppraised is present: the name is outside the published catalog and was not computed on this server."

changedOutput schema / properties / notAppraised / description

Previous value: -"The name that was not computed here. Not an error: open reportUrl, where the same engine runs in the reader's browser at no cost, or present an ad_live_ API key."New value: +"The name that was not computed here. Not an error: open reportUrl, where the same engine runs in the reader's browser at no cost."

First observedSep 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses genuinely useful traits: determinism ('same name, same figure'), that confidence is an internal 0-100 score rather than a probability, the four possible response modes (cached, catalog, stored, none), and credit-consumption rules. The credit rules are stated repeatedly and are hard to parse, which dilutes but does not negate the added behavioral value.

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

Conciseness2/5

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

The credit/cache rules are stated at least twice nearly verbatim ('Cached answers, keyless catalog figures and public stored intervals use no API credits...' then 'MCP cache hits use no API credits...'), bloating the description with redundancy. The core purpose is front-loaded, but the back half is a tangled wall of authorization, billing and URL detail that obscures the actionable facts.

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 an output schema exists, return values need not be spelled out, yet the description still usefully enumerates the response variants including the empty-result case ('no figure but a browser report link, 3 nearest published names... and a next step'). The main omission is that the auth/credit conditions are so muddled that an agent may not reliably know when a call costs credits.

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?

There is a single parameter with 100% schema description coverage, and the schema already documents the domain format including URL acceptance. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The opening states a specific verb and resource: 'Estimate the fair value of one domain name with its low/high interval.' It also distinguishes itself from siblings by routing sales browsing to search_recorded_sales and find_comparable_sales, so an agent can tell what this tool is and is not for. The core purpose is clear despite the surrounding clutter.

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 names two explicit alternatives with their purposes ('Use search_recorded_sales to browse sales and find_comparable_sales for just the five nearest sales') and clarifies that a paid purchase is 'a separate paid purchase, not a charge for this MCP lookup,' distinguishing it from purchase_appraisal. No explicit when-not-to-use condition is given, but the routing guidance is concrete.

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

All audit.domains - Domain Valuation 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.

Resources

Need Help?