audit.domains - Domain Valuation

Compare and rank domain names

compare_domains

Read-onlyIdempotent

Appraise up to 10 domain names and rank them by estimated fair value, flagging adjacent pairs whose intervals overlap so their order is not separable. Use run_bracket instead for one champion from a head-to-head tournament of up to 8 names, tiers not values. Deterministic. More than 10 names, or a request cut off by the engine budget, returns a handoffUrl that runs the same engine free in the browser. Without a key, only catalog and recently appraised names get a figure; other names return a report link, nearest published names and a next step instead. MCP cache hits use no API credits; without a key, catalog fallbacks are free. 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domains`	Yes	Domain names to rank, such as example.com. Up to 10 are appraised here; 11 to 16 return handoffUrl only.

Output Schema

TableJSON Schema

Name	Required	Description
`next`	No	The one step that moves this name forward: {tool, arguments} to call next on this server, or {url} to open; why says what it gets. Null when nothing here does (for a free name, registering it at a registrar).
`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.
`ranked`	Yes
`citation`	Yes
`handoffUrl`	No	Present when this request could not run every name here (over the tool cap, or cut off by the per-request engine budget): a link to the free page that runs the same deterministic computation for all of them in the reader's browser. Give it to the user rather than retrying.
`notAppraised`	No	Names that did not run here (over the tool cap, or cut off by the request budget). They are absent from the ranking, not ranked last - see handoffUrl.
`inseparablePairs`	Yes	Adjacent pairs whose published intervals overlap; the ordering between them is not separable by this method.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

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."

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / next

Added value: +{
+  "description": "The one step that moves this name forward: {tool, arguments} to call next on this server, or {url} to open; why says what it gets. Null when nothing here does (for a free name, registering it at a registrar).",
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / domains / description

Previous value: -"The domain names to compare. Up to 10 are appraised here; 11-16 return handoffUrl instead."New value: +"Domain names to rank, such as example.com. Up to 10 are appraised here; 11 to 16 return handoffUrl only."

First observedSep 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial context an agent cannot get elsewhere: deterministic results, credit consumption rules (cache hits free, catalog fallbacks free without a key, one credit on an authorized keyed cache miss), rate limits, server budget, key-scope requirements, and error behavior on rejected keyed runs. This is unusually rich disclosure for a read-only tool.

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?

Front-loaded with the core action and the sibling alternative before the operational detail, and every sentence carries information (limits, cost, fallbacks, errors). It is dense and long, but the pricing and key-scope sentences earn their place because they affect whether an agent should call it at all.

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?

With an output schema present, return values need not be explained, and the description covers everything else an agent needs: input cap, sibling routing, determinism, authentication/scoping, credit cost, cache behavior, handoff behavior, and failure modes. Nothing material is missing for a single-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description reconciles a real discrepancy: the schema allows 1–16 items while the description clarifies that only up to 10 are appraised and 11–16 yield a handoffUrl only. That interpretation of the cap boundary adds meaning beyond the raw maxItems constraint.

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 and resource ('Appraise up to 10 domain names and rank them by estimated fair value') with a precise output concept (overlapping intervals flagged as non-separable). It explicitly names the sibling it is not — run_bracket for head-to-head tournaments — so an agent can route between them without opening either schema.

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 when-to-use-this vs when-to-use-the-alternative: this tool for ranked fair values of up to 10 names, run_bracket for a single champion from a tournament of up to 8. It also names the boundary condition (>10 names or budget cutoff) and the fallback behavior, leaving nothing to inference.

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?