Skip to main content
Glama

Read owned domains

domainOwned
Read-onlyIdempotent

Read the signed-in account’s domains registered through Tofu, including domains detached from an app. registration carries stored expiry, autoRenew, verification deadline and transfer lock; renewal carries the recorded renewal stage and next dates. paymentStanding of held or unknown reports held or undetermined payment standing; this status read establishes no write eligibility. connections list owned app hostnames with id, status, next step and serving lane. available false means registrations could not be read; connectionsRead unavailable or limited means an empty connection list does not prove a name is disconnected; a null renewal is unavailable or absent. asOf dates this stored read; syncedAt dates the registrar sync. This tool polls no provider, changes no renewal setting, reveals no owner contact details or transfer codes, and makes no payment. Human domain actions are on the dashboard’s Domains page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
asOfYes
limitYes
domainsYes
availableYes
truncatedYes
connectionsReadYes
renewalsAvailableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 closed-world, yet the description adds substantial independent context: it polls no provider, changes no renewal setting, exposes no owner contacts or transfer codes, and makes no payment. It also disambiguates degraded states ('available false means registrations could not be read', 'connectionsRead unavailable or limited means an empty list does not prove a name is disconnected') and defines the two timestamps, which directly prevents an agent from over-reading an empty result.

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 purpose is front-loaded, but the body is a dense semicolon-chained block that mixes return-field semantics, negative guarantees, failure-mode caveats and timestamp definitions without paragraphing. Domain-internal vocabulary ('Tofu', 'serving lane') appears without definition, so the text is heavier to parse than its information content requires.

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 an output schema present the description need not restate return fields, yet the field-level notes it does give (paymentStanding held/unknown, null renewal, asOf vs syncedAt) are the non-obvious parts an agent could misread from the schema alone. Coverage is strong for a zero-parameter read; the main omission is any pointer to which sibling tool handles the write-side actions besides the dashboard.

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 takes no parameters, so parameter semantics carry no burden and the baseline of 4 applies. The description adds no argument syntax, correctly, since there is nothing to pass.

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 opening sentence names a specific verb and resource ('Read the signed-in account's domains registered through Tofu') plus a scope qualifier ('including domains detached from an app'), which is far beyond a restatement of the name. It stops short of naming which sibling (e.g. domainRecords, domainVerify) to use for adjacent tasks, so an agent must still infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: this is the read-side counterpart to mutations, and the closing line routes human/write actions to the dashboard's Domains page. There is no explicit 'use this instead of X when Y' and no statement of prerequisites, so the guidance is only adequate for a zero-parameter read.

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