Skip to main content
Glama

Get domain prices

get_domain_pricing
Read-only

List available domain TLDs and their registration prices. Optionally filter by a single TLD, or check a full domain name to get availability and premium pricing info. Supports currency conversion (EUR/USD) and gross/net display.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_domain_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldNoOptional TLD to look up (e.g. 'com')
domainNoFull domain to check availability and premium fee (e.g. 'example.com')
displayNoPrice display mode (default: gross)
currencyNoCurrency for prices (default: EUR)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful context — currency conversion (EUR/USD) and gross/net display — but says nothing about price freshness, whether taxes/fees are included, or any rate limits on price lookups.

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?

Three short sentences, front-loaded with the primary listing behavior, then the filtering modes, then supported options. No filler, though the middle sentence packs three ideas together.

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 read-only pricing tool with all-optional, fully documented parameters, the description covers the main modes and options. The only gap is what the response looks like when checking a domain (availability plus premium fee), which is not stated and there is no output schema to fall back on.

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 coverage is 100% with enum-typed display and currency plus described tld and domain, so the schema does the heavy lifting. The description restates those parameters ('filter by a single TLD', 'check a full domain name', 'currency conversion', 'gross/net display') without adding format or precedence details, so it lands at the baseline.

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?

States a specific verb and resource: 'List available domain TLDs and their registration prices', plus two alternative modes (filter by TLD, or check a full domain for availability/premium pricing). The purpose is clear without opening the schema, though it doesn't explicitly differentiate itself from the availability-oriented sibling check_domain.

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?

Gives mode guidance tied to parameters ('Optionally filter by a single TLD, or check a full domain name to get availability and premium pricing info'), which implicitly tells the agent which input to supply for which outcome. It stops short of explicit when-to-use vs. alternatives or any stated exclusions.

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.