Help by DeltaBreen

add_domain

Add a domain the workspace's form is on. The answer has the tag, DNS record or file that proves it; then call verify_domain. Owner only.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain the form is on, without https://, like shop.example.com.
`product_ids`	No	The sites whose form is on this domain (ids from list_products). Leave out for every site.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026
- changedInput schema / properties / product_ids / type
```
Previous value: -[
-  "array",
-  "null"
-]New value: +"array"
```
First observedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With annotations already declaring readOnly=false, destructive=false, idempotent=false, and openWorld=false, the description adds useful behavior: the response includes proof material and verification must follow. It also discloses the owner-only restriction. It does not explain duplicate-domain handling or other failure behavior beyond the annotation hints.

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?

The description is three short sentences and front-loads the action. Every sentence adds useful information: the purpose, the returned proof plus next step, and the owner-only restriction.

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?

Given full schema coverage and existing annotations, the description is mostly complete: it explains the action, returned proof, follow-up verification, and permission requirement. It leaves some edge-case behavior unstated, such as what happens for duplicate domains or how failures are reported.

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%, so the schema already documents both parameters, including the optional product_ids behavior. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Add a domain' associated with the workspace's form. It also names the required follow-up tool, verify_domain, which helps distinguish this from the verification step and from obvious siblings like list_domains or remove_domain.

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 clear usage context by saying the answer contains the tag, DNS record, or file that proves ownership and that verify_domain should be called next. It also states 'Owner only,' which is an important prerequisite. It does not explicitly mention when not to use it or whether list_domains should be checked first.

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

All Help by DeltaBreen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?