Skip to main content
Glama

DNS provider profile and market share

dns_provider_info
Read-onlyIdempotent

Retrieve a DNS provider's domain count, market share, rank, share changes, and one-year growth by alias, name, or nameserver root, including the alias needed to list its domains.

Instructions

Number of domains using a DNS (nameserver) provider, its market share and rank, share change over 30 days and one year, one-year growth. Matches by alias ("cloudflare"), name or nameserver root ("awsdns"). The returned alias is what get_download_url takes as dns_alias for the list of all domains using the provider. 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": {
      "query": "<query>"
    },
    "name": "dns_provider_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesProvider alias, name or nameserver root, e.g. "cloudflare"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful non-structural context: the operation is free, and the 'alias' value it returns is the input key for get_download_url, which is behavioral/output semantics an agent cannot derive from annotations alone.

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 compact sentences, front-loaded with the returned payload and followed by matching rules and the downstream alias handoff. Dense but no filler; the metric enumeration is long yet each item is substantive.

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 carries the return-value burden and does so by listing the fields returned. Missing only edge behavior (no-match responses, ambiguity when a query matches multiple providers), which is minor for a free read-only lookup.

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?

Schema coverage is 100%, so the baseline is 3, and the description goes slightly beyond it by spelling out the three matching modes (alias, name, nameserver root) with examples such as "cloudflare" and "awsdns". It does not explain case-sensitivity or what happens on a non-matching query.

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 exact resource (DNS/nameserver provider profile) and enumerates the returned metrics: domain count, market share, rank, 30-day and one-year share change, and one-year growth. It also states the accepted input forms (alias, name, nameserver root), so an agent can distinguish it from siblings like registrar_info or domain_rank 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 Guidelines4/5

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

It clearly frames the lookup context and adds a concrete downstream routing hint: the returned alias is the dns_alias get_download_url expects for listing all domains on that provider. It does not state when NOT to use it or name a competing sibling, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.