Skip to main content
Glama
Sign In

AppDeploy

by ai.appdeploy
OverviewDiscussionsAdmin

Get custom domain instructions

get_custom_domain_instructions
Read-onlyIdempotent

Use this tool with app_id to check custom-domain status or get DNS and verification instructions before connecting a domain. MCP version 2.12.

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

Input Schema

NameRequiredDescriptionDefault
app_idYesTarget app id
mcp_versionNoSet to "2.12", the MCP version in this tool's description. Use this tool's version, not another tool's version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mcp_version / description
      Previous value: -"Set to \"2.11.7\", the MCP version in this tool's description. Use this tool's version, not another tool's version."New value: +"Set to \"2.12\", the MCP version in this tool's description. Use this tool's version, not another tool's version."
  2. Changed1 schema field changed
    • changedInput schema / properties / mcp_version / description
      Previous value: -"Set to \"2.11.0\", the MCP version in this tool's description. Use this tool's version, not another tool's version."New value: +"Set to \"2.11.7\", the MCP version in this tool's description. Use this tool's version, not another tool's version."
  3. Changed1 schema field changed
    • addedInput schema / properties / mcp_version
      Added value: +{
+  "description": "Set to \"2.11.0\", the MCP version in this tool's description. Use this tool's version, not another tool's version.",
+  "maxLength": 32,
+  "minLength": 1,
+  "pattern": "^\\d+\\.\\d+(?:\\.\\d+)?$",
+  "type": "string"
+}
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds workflow context (use before connecting a domain) but says nothing about what the status output contains or how it behaves when no domain is configured.

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, front-loaded with the action and the workflow context, with no filler. The trailing version note is necessary because the schema requires that exact value.

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?

A simple two-parameter read-only tool with full schema coverage and rich annotations; no output schema exists, but the description conveys enough about what is returned (status, DNS and verification instructions) for an agent to call it correctly.

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 app_id and mcp_version are already documented in the schema. The description only restates that app_id is the input and repeats the version string, adding no semantics beyond the schema.

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?

States a specific verb+resource: check custom-domain status or retrieve DNS/verification instructions for an app_id. It implicitly differentiates from add_custom_domain and verify_custom_domain via the 'before connecting a domain' framing, though it never names those siblings explicitly.

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?

Gives clear usage context ('check custom-domain status or get DNS and verification instructions before connecting a domain'), which implies the read-first workflow preceding add_custom_domain/verify_custom_domain. It does not explicitly state exclusions or name the alternative tools.

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

All AppDeploy 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