Skip to main content
Glama

Domains anzeigen

get_domains
Read-only

Den vollständigen Domainbestand des Kunden abrufen: sowohl die bei turbopress registrierten Domains (mit Ablaufdatum, Registrar-Status und Auto-Renew) als auch die Domains, die bei turbopress gehostet, aber bei einem anderen Anbieter registriert sind. Eine Domain ohne Ablaufdatum ist deshalb kein Fehler, sondern woanders registriert; Test-Subdomains (.trial.turbopress.de) werden nie registriert und haben ebenfalls kein Ablaufdatum. Gehostete Domains lassen sich mit allen übrigen Werkzeugen bearbeiten, unabhängig davon, wo sie registriert sind. Je gehosteter Domain stehen außerdem Tarifart und WordPress-Stand da: WordPress-Werkzeuge (Updates, Plugins, Staging, WordPress-Backups, Cache, Härtung) nur für Domains mit WordPress verwenden bzw. anbieten; Domains im Tarif AI Launch sind statische Websites ohne WordPress/PHP – dort für Änderungen an der Website die deploy_-Werkzeuge nutzen; E-Mail-Postfächer und DNS-Einträge lassen sich wie gewohnt verwalten, alles andere nur lesen.

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_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description explains important data quirks: missing expiry dates can mean external registration, trial subdomains are never registered, and hosted domains may be edited regardless of registrar. It also clarifies that the response includes tariff type and WordPress status, and that everything other than email/DNS is read-only, which meaningfully supplements the annotations.

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?

The description is front-loaded with the core purpose and avoids filler, but it is a dense paragraph that includes considerable downstream tool guidance. That information is useful, though the length is notable for a zero-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 burden of explaining return data, and it does so thoroughly: registered versus hosted domains, expiry-date interpretation, trial subdomains, tariff type, and WordPress status. It also covers follow-up constraints, making the definition complete enough for an agent to call and use the result correctly.

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 tool has zero parameters, so the baseline score is 4. There are no parameter semantics to clarify, and the schema's empty properties object is consistent with the description.

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 states a specific verb and resource: retrieve the customer's complete domain inventory, including both turbopress-registered and externally registered but hosted domains. It is clear what the tool returns, but it does not explicitly distinguish get_domains from the sibling get_wordpress_sites tool.

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 description gives clear context for using the returned domain data, including which tools apply to WordPress domains, AI Launch static sites, email accounts, and DNS records. It does not explicitly state when to prefer get_domains over a WordPress-specific sibling listing, but no direct alternative for a complete domain inventory is named.

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