Skip to main content
Glama

Subdomains and lookalikes of a website's domain

get_domain_watch
Read-only

For an http or api monitor on Pro and Business plans: the website's registered domain, its subdomains from certificate transparency logs (crt.sh, which can be days or weeks behind) with where each points and any CNAME to a service that reports no site there (subdomain_alerts), and the registered typo and look-alike spellings of the domain with their addresses, mail servers and registration dates (lookalike_alerts). Free.

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": {
      "id": "<id>"
    },
    "name": "get_domain_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare this as a read-only operation and not open world, so the agent knows it is safe. The description adds relevant context beyond the annotations: certificate transparency data from crt.sh can be days or weeks behind, the tool is free, and it only applies to http/api monitors on paid plans. Missing are details about how empty results or failures are surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded eligibility clause is good, but everything else is packed into one long sentence with several nested parentheticals, which makes it awkward to parse. The field list is informative, yet a short bulleted or separate-clause structure would communicate the same contents more cleanly.

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 no output schema, the description has to describe what is returned, and it does so in detail, covering both subdomain_alerts and lookalike_alerts and their contents. It stops short of covering result shape, pagination or empty-result behavior, which leaves a modest gap for a data-returning 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?

The single parameter has full schema coverage and the schema itself points the caller to list_monitors. The description adds real meaning on top of that by restricting the acceptable ID to an http or api monitor on a Pro or Business plan, which is a constraint the schema does not encode.

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?

The description names the concrete resources returned: the registered domain, subdomains from certificate transparency logs with their destinations, and registered typo/look-alike spellings with addresses, mail servers and registration dates. That is specific enough for an agent to tell this apart from sibling tools such as get_monitor or get_website_changes without opening a schema.

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 definition states an eligibility condition, 'For an http or api monitor on Pro and Business plans,' which tells the agent exactly which monitor IDs are valid inputs. It does not name alternatives or explain when not to call the tool, so there is no explicit routing guidance.

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