Skip to main content
Glama

Suggest a free hostname

suggest_runtime_domain
Read-onlyIdempotent

Returns an available project hostname under the selected DeployMonster hosting domain. It does not create a project or reserve the suggested address.

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": {
      "name": "<name>"
    },
    "name": "suggest_runtime_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by clarifying that nothing is created or reserved, meaning the suggestion is advisory and availability is not guaranteed. It does not mention whether results are cached or how quickly a suggestion might become stale.

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?

Two short sentences, zero filler, with the primary behavior stated first and the scope caveat second. Every clause earns its place.

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

Completeness3/5

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

For a simple read-only tool with two parameters and no output schema, the description correctly covers scope and side-effect absence. However, with 0% parameter documentation and no explanation of the returned hostname's shape (full URL vs. subdomain label), an agent must guess what it receives and how to pass 'name'.

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% for both parameters, so the description carries the full burden. It only obliquely hints that 'domain' selects the hosting domain ('under the selected DeployMonster hosting domain') and says nothing about what 'name' means, whether it is a desired project name, or what happens if it is unavailable or too long.

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 gives a specific verb and resource: it returns an available project hostname under a chosen hosting domain. The second sentence clarifies the negative scope (it does not create a project or reserve the address), which separates it from project-creation siblings. It stops short of naming an actual alternative tool, but the intent is unambiguous.

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: an agent can infer this is a pre-check before creating or configuring a project domain, and the 'does not create' clause implies it is a non-committal probe. There is no explicit when-to-use/when-not guidance and no named sibling alternative such as create_project or manage_project_domain.

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