Skip to main content
Glama

List domains

domains
Read-onlyIdempotent

List one owned project’s connected hostnames and the providers Tofu could write DNS records for — the dashboard’s Domains page, read. This is the read for “is my domain set up?”: it names every hostname connected to the project and what each is waiting for. domains[] gives each connection’s id, status, message, ownership TXT challenge, routing dnsRecords, providerVerification records and next: the step it waits on, who acts (waitingOn) and whether one-click can write its records (oneClick). providers[] says which one-click providers Tofu has configured and what the owner agrees to (consentNote); an unconfigured one is reported as unavailable rather than offered. enabled: false means no new hostname can be connected to this project right now, which is not the same as a project with no domains. It writes nothing, resolves no DNS and returns no credential.

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": {
      "projectId": "<projectId>"
    },
    "name": "domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
domainsYes
enabledYes
providersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the two-part return shape (domains[] vs providers[]), that unconfigured providers are reported as unavailable rather than offered, and that enabled:false means no new hostname can be connected — explicitly not the same as zero domains. That last distinction is a real behavioral trap an agent would otherwise misread.

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?

Purpose is front-loaded and the enabled:false caveat earns its place, but the middle stretch enumerating domains[] and providers[] fields (id, status, message, ownership, dnsRecords, providerVerification, next, waitingOn, oneClick, consentNote) largely restates an output schema that already exists. That field-by-field walkthrough is the bulkiest part of the definition and the least necessary.

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?

For a single-parameter read with rich annotations and a published output schema, nothing an agent needs is missing: scope, safety, the enabled:false edge case, and provider-availability semantics are all covered, and return values need not be explained further.

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?

With one parameter and 0% schema description coverage, the description carries the burden and does add meaning: "one owned project's" signals the projectId must be a project the caller owns, implying the authorization scope of the lookup. It does not state the uuid format or what happens for an unowned/unknown project, keeping it below 5.

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?

States a specific verb and resource: lists one owned project's connected hostnames plus the providers Tofu can write DNS records for, and anchors it to the dashboard's Domains page as a read. An agent can distinguish this from the app*/database* siblings without opening any 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?

Frames the use case concretely with "the read for 'is my domain set up?'" and clarifies the negative: it writes nothing, resolves no DNS, returns no credentials. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so a 4 rather than a 5.

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