Skip to main content
Glama

thanaton_manage_domains

List, add, or delete a project's custom domains and verify SSL/TLS provisioning to keep domain routing and certificates correctly configured.

Instructions

List, add, or delete custom domains and verify SSL/TLS provisioning for a project.

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": {
      "project_id": "<project_id>",
      "action": "<action>"
    },
    "name": "thanaton_manage_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform
domainNoDomain name (e.g., api.example.com), required for add and delete
project_idYesTarget project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, yet it says nothing about the destructive, likely irreversible nature of delete, whether DNS must already point at the platform, or how SSL provisioning is verified or how long it takes. The mention of SSL/TLS verification without a matching action also muddies rather than clarifies behavior.

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?

A single front-loaded sentence with no filler, enumerating the operations first. It is efficient, though the trailing SSL/TLS clause is confusing rather than additive.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with a delete path, no annotations, and no output schema, the description should at least cover destructive consequences and DNS/SSL prerequisites. As written, an agent cannot tell what deletion destroys or what a successful add returns.

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 coverage is 100% and each parameter already has a description, including that domain is required for add and delete, so baseline is 3. The description adds only the notion that operations are scoped 'for a project' and nothing about domain format, validation, or what happens if domain is omitted.

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 names concrete operations (list, add, delete) on a concrete resource (custom domains) scoped to a project, so an agent can tell what it does without opening the schema. It falls short of 5 because it also claims a 'verify SSL/TLS provisioning' capability that has no corresponding action in the enum, blurring the actual scope, and it does not distinguish itself from siblings such as thanaton_manage_routes.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives despite many adjacent management tools (routes, deploy hooks, env) in the catalog. Usage is only implied by the verb list.

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

Deploy Server

Other Tools