Skip to main content
Glama

Premium Domain Changes Monitor (7d)

domain_changes
Read-onlyIdempotent

List registration and status changes to premium .com domains (short 1-4 letter and high-value single-word names) over a rolling 7-day window, filtered by change reason and length.

Related: whois, ns_reverse.

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

Input Schema

NameRequiredDescriptionDefault
tldNoTLD filter (e.g., 'com')
pageNoPage number for pagination
sortNoSort order
lengthNoPrefix length filter (characters before TLD)
reasonNoFilter by change type
keywordNoSearch by domain or keyword within the monitored pool
has_digitNofalse = letters only (default), true = contains digits, all = digits only

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message when success is false
totalNoNumber of results on this page
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed1 schema field changed
    • removedOutput schema / properties / data / items / properties / combination
      Removed value: -{
      -  "description": "Word segmentation of the prefix",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedInput schema / properties / has_digit / description
      Previous value: -"false = letters only, true = contains digits, all = no filter"New value: +"false = letters only (default), true = contains digits, all = digits only"
  4. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description does add real behavior beyond that: the window is fixed at a rolling 7 days and the monitored pool is limited to premium short/single-word .com names. However, it claims the pool is '1-4 letter' while the schema's length enum exposes 5-8 and 9+ buckets, an internal inconsistency an agent could trip over.

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?

A single front-loaded sentence states scope, window, and filters with no filler, followed by a short related-tools line. Efficient and well ordered, though the 'Related:' fragment is too terse to earn its place as written.

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?

With an output schema present, return values need no explanation, and all seven parameters are documented in the schema. The description supplies the essential scope (7-day window, premium-name pool) that the schema cannot convey; the main gap is the unresolved 1-4 letter versus 5-8/9+ length-enum discrepancy.

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%, so the baseline is 3. The description only echoes two of the seven filters ('change reason and length') and adds no syntax, defaults, or interaction guidance for keyword, has_digit, sort, page, or tld. Its '1-4 letter' framing actually conflicts with the length enum values, which is a small negative against an otherwise schema-complete tool.

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 description gives a specific verb and resource ('List registration and status changes to premium .com domains') with an explicit scope: rolling 7-day window, short 1-4 letter and high-value single-word names. It is far more specific than the title alone, but the only sibling differentiation is the vague 'Related: whois, ns_reverse' line, which does not tell an agent how this differs from monitor, deleted, or expired.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. The 'Related: whois, ns_reverse' note names adjacent tools but supplies no condition that would select one over the other, and with siblings like monitor, active, deleted, and expired in the catalog, the agent is left to infer the boundary entirely.

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.