Skip to main content
Glama

domain_check

Read-onlyIdempotent

Check if a domain is available for purchase and get the price.

Example:

{ "domain": "acmedash.com" }
// Returns: { "available": true, "price": "$12.00/year" }

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check, e.g. mybooking.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety and repeatability are covered. The description adds real value by disclosing the return payload (availability flag and price) in the example, which matters since there is no output schema, but it says nothing about failure modes, invalid domains, or pricing caveats.

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?

One declarative sentence front-loads the purpose, followed by a minimal input/output example that earns its space by encoding the response shape. No redundant restatement of the name or title.

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 single-parameter read tool with full annotation coverage, the definition supplies purpose, a format example, and the return shape, which covers what an agent needs to call it correctly. Minor gaps remain around error behavior and currency/price variability.

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% and the single parameter is documented in the schema, so baseline 3 applies. The example input 'acmedash.com' reinforces the expected bare-domain format (no scheme or path), which is a small but genuine clarification.

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 pair and resource: checks domain availability and returns a purchase price. The 'for purchase' framing naturally separates it from a buying operation like domain_buy, so an agent can select it without opening the schema.

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?

Usage is only implied — an agent can infer 'check before you buy' — but the description never says when to use this versus domain_buy, nor does it state any exclusions or prerequisites (e.g., that it must run before a purchase).

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.

Resources