Skip to main content
Glama

DNSFix

Get a watched domain

get_domain
Read-onlyIdempotent

The latest check for one of your watched domains: grade, top problems and the record to paste. Needs a connected DNSFix™ account with domain watching.

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

Input Schema

NameRequiredDescriptionDefault
detailNoOptional: true returns every check in full. Leave it out for the short answer.
domainYesA domain name, for example yourbusiness.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 the safety profile is covered. The description adds valuable context beyond that: the account/watching prerequisite and the shape of the returned content (grade, top problems, paste-ready record). It omits failure behavior for an unwatched or unknown domain.

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?

Two compact sentences: the first front-loads what you get back, the second front-loads the prerequisite. No filler, no restatement of the 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?

With no output schema, the description usefully enumerates the return payload (grade, top problems, record to paste), which is exactly the missing piece for an agent deciding whether to call it. Only the error/non-watched-domain path and pagination or currency of 'latest' are unaddressed, which is a minor gap for a 2-parameter read tool.

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%, with both `domain` and `detail` documented inline including the 'leave it out for the short answer' default. The description adds no parameter-level meaning — 'latest check' merely echoes detail=false — so the baseline 3 applies.

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 names a specific resource ('one of your watched domains') and a specific payload ('the latest check ... grade, top problems and the record to paste'), which an agent can distinguish from a fresh scan or a history listing. It stops short of naming a sibling tool, so it lands at 4 rather than 5.

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?

It gives a clear precondition — a connected DNSFix™ account with domain watching — which implicitly excludes domains the user hasn't added. However, it never states the negative case (what to call if the domain isn't watched, e.g. scan_domain) or what happens on an unwatched domain, so no explicit alternative routing.

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