Skip to main content
Glama

Domain Market Price Check

market_price
Read-onlyIdempotent

Check whether a domain is listed for sale on a supported aftermarket and, if it is, the asking price. Returns for_sale with the asking price in USD, make_offer when it is listed without a fixed price, or not_found when no listing was found. Coverage is limited to a few marketplaces, so not_found does not mean the domain is not for sale elsewhere.

Related: available, aged.

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": "market_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name (e.g., 'example.com')

Output Schema

NameRequiredDescriptionDefault
errorNo
domainNo
statusNoMarket status: for_sale, make_offer, or not_found
messageNo
successNo
currencyNoPrice currency (e.g., USD)
estimated_priceNoSeller's listing price (only when status=for_sale)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success",
      -  "domain",
      -  "status"
      -]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world semantics, so the description's added value is the marketplace-coverage limitation and the meaning of each return state — genuinely useful behavioral context. The return-state enumeration overlaps with the output schema, keeping it from a 5.

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, then result states, then the coverage caveat and related tools — no filler. The result-state sentence duplicates what the output schema already declares, which is a small redundancy in an otherwise tight definition.

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?

For a one-parameter read-only lookup with an output schema, the description supplies everything an agent needs: what it returns, what a negative result implies, and where to look next. No material gap remains.

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 fully documented parameter (100% schema coverage), so the schema carries parameter meaning entirely. The description adds no format, normalization, or IDN guidance beyond the schema's own example.

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: checks whether a domain is listed for sale on an aftermarket and returns the asking price. Concrete result states (for_sale, make_offer, not_found) make it clearly distinct from siblings like 'available' or 'whois'.

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?

The coverage caveat ('not_found does not mean the domain is not for sale elsewhere') tells the agent when to distrust a negative result, and 'Related: available, aged' points at adjacent checks. It stops short of explicitly stating when to prefer 'available' or 'price' instead, so routing is implied rather than prescribed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.