Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Coolify: Get server domains

coolify_get_server_domains
Read-only

Retrieve all domains configured on a specific server to inspect site routing and domain assignments.

Instructions

[UNIFIED] Get all domains configured on a specific server.

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": {
      "site": "<site>",
      "uuid": "<uuid>"
    },
    "name": "coolify_get_server_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.7/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this is a non-mutating read, so the description's burden is to add context beyond that. It adds only the notion of 'all domains,' with no information on whether that includes wildcard/redirect entries, whether an empty result is possible, or what shape the domains come back in.

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 short sentence that front-loads the action and scope. The only wasted token is the '[UNIFIED]' tag, which conveys nothing to an agent selecting a tool.

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?

With two required, undocumented parameters, no output schema, and no annotation beyond readOnlyHint, the description leaves the caller without enough information to construct a correct call. It should at minimum explain the roles of 'site' and 'uuid'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither of the two required parameters ('site', 'uuid') is explained anywhere. The phrase 'on a specific server' hints that 'uuid' identifies the server, but 'site' is entirely unaccounted for, so the caller must guess which field carries which value.

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 a specific verb and resource ('Get all domains') scoped to 'a specific server,' which lets an agent distinguish it from coolify_get_server and coolify_get_server_resources. The '[UNIFIED]' prefix is an internal marker that adds no meaning for a caller.

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 statement of when to use this tool versus the other server-related siblings, no prerequisites, and no exclusions. The only implied guidance is that the caller must already know which server they want domains for.

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