Skip to main content
Glama

shiply

by now.shiply
OverviewDiscussionsAdmin

Point a subdomain at a site

add_subdomain
Idempotent

Serve an owned site at . (use subdomain "@" or "" for the apex — apex needs a provider with CNAME flattening/ALIAS, e.g. Cloudflare). Auto-registers the parent domain. Returns the CNAME record to add (host -> cname.shiply.now); the certificate issues automatically once DNS resolves. Poll with check_domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesowned site slug to serve there
domainYesregistrable parent domain, e.g. example.com
subdomainYessubdomain label, or "@"/"" for the apex

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"registrable parent domain, e.g. example.com"
    • addedInput schema / properties / slug / description
      Added value: +"owned site slug to serve there"
    • addedInput schema / properties / subdomain / description
      Added value: +"subdomain label, or \"@\"/\"\" for the apex"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations provide openWorldHint and idempotentHint, indicating safe side effects and idempotency. The description adds behavioral details: auto-registers parent domain, returns CNAME record, and automatic certificate issuance after DNS resolves. This provides useful context beyond annotations, though it could mention if there are any destructive steps.

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?

The description is two sentences, covering the main function, apex handling, follow-up action, and return value. It is efficiently written with zero wasted words, front-loaded with the core purpose, and easy to parse.

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?

Given the tool's complexity (3 required params, no nested objects), the description is complete. It explains the return value (CNAME record) and the subsequent step (poll with check_domain). The presence of an output schema (not shown) further reduces the need to describe return format. No gaps identified.

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% with clear descriptions for each parameter. The description reiterates the schema's definitions (e.g., 'owned site slug', 'registrable parent domain') but does not add new meaning or format details. Baseline 3 is appropriate as schema already documents the parameters effectively.

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?

The description clearly states the action ('Serve an owned site at <subdomain>.<domain>') and specifies the resource (subdomain on a domain). It distinguishes from siblings like add_domain by focusing on subdomain mapping and includes special handling for apex. The verb 'point' and resource 'subdomain' are specific and unambiguous.

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?

The description provides clear usage context: use when you want to serve a site at a subdomain. It mentions apex requirements and advises polling with check_domain. However, it does not explicitly state when not to use this tool or list alternatives (e.g., add_custom_domain), so it's slightly lacking in exclusion guidance.

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

All shiply toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources