Skip to main content
Glama
Sign In

Roar AI

by com.roar-ai
OverviewDiscussionsAdmin

Attach a custom domain

add_app_domain

Attach a domain the customer owns to an app. THIS DOES NOT MAKE IT LIVE: it returns the DNS records they must create at their registrar, and the domain stays pending until those records resolve and a certificate is issued. Tell them the records, then use list_app_domains to check whether it has gone live. For a free address on our own domain, use add_roar_domain instead.

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": {
      "appId": "<appId>",
      "domain": "<domain>"
    },
    "name": "add_app_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesThe app id returned by deploy_app or list_apps
domainYesThe domain the customer owns, e.g. app.theircompany.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / appId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only say it's a non-destructive, non-read-only, non-idempotent call; the description adds the crucial real behavior: the domain stays pending until DNS records resolve and a certificate is issued, and the call returns those records for the customer's registrar. It doesn't cover edge cases like re-adding an already-attached domain or what happens if the customer doesn't own the domain, which is why it falls short of a 5.

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?

Three tight sentences: the action, the critical caveat in capitals up front, then the follow-up and the alternative. Zero filler and every sentence carries decision-relevant information.

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 2-parameter, non-destructive mutation with full schema coverage and no output schema, the description supplies everything an agent needs: what it returns (DNS records), that the result is asynchronously pending, and how to verify completion. Nothing material is missing.

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 both appId (with its 'returned by deploy_app or list_apps' hint) and domain are already documented in the schema. The description reinforces the ownership constraint on domain but adds no format or validation detail beyond what the schema provides, so the baseline 3 applies.

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 ('Attach a domain the customer owns to an app') and immediately distinguishes it from the sibling add_roar_domain, which handles free addresses on our own domain. An agent can choose between the two without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says what this does NOT do ('THIS DOES NOT MAKE IT LIVE'), names the follow-up tool (list_app_domains) and the condition for using it (waiting for records to resolve), and routes the alternative case to add_roar_domain. This is the full when/when-not/alternatives triad.

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

All Roar AI toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources