Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Connect Blog Custom Domain

connect_blog_domain
Destructive

Claim a custom hostname for the workspace blog. Returns DNS targets to configure. The blog must already have a title.

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

Input Schema

NameRequiredDescriptionDefault
DomainYesHostname to claim, e.g. blog.example.com.

Output Schema

NameRequiredDescriptionDefault
DomainYesClaimed hostname if any.
StatusYespending, awaiting_dns, issued, failed, or empty.
DNSCnameYesCNAME target for DNS.
CheckedAtYesISO-8601 last check if set.
ErrorKindYesError kind if any.
LastErrorYesLast error message if any.
ConfiguredYesWhether certificate manager is configured.
DNSARecordYesA-record IP for DNS.
CertExpiresAtYesISO-8601 cert expiry if set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the full profile: destructiveHint=true, idempotentHint=false, openWorldHint=true. The description adds real value by disclosing that the call returns DNS targets requiring follow-up configuration, but it does not address what happens if a domain is already claimed, whether re-claiming replaces it, or that verification is asynchronous — notable gaps for a destructive, non-idempotent mutation.

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 sentences, zero waste, with the primary action front-loaded and the return-shape hint second. The precondition sentence earns its place by preventing a class of failed calls.

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?

For a one-parameter tool with a full schema, an output schema (so return values need no explanation), and complete annotations, this is close to sufficient. The only shortfall is the absence of failure/replacement semantics for the destructive claim itself.

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 a concrete example (blog.example.com) plus min/max length constraints, so the schema carries the load. The description adds only the word "hostname", which is a modest restatement rather than new meaning — baseline 3 applies.

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?

"Claim a custom hostname for the workspace blog" gives a specific verb (claim) and resource, clearly distinct from siblings like get_blog_custom_domain and remove_blog_custom_domain. It also states the side effect (returns DNS targets), though it never names the sibling read/remove tools explicitly.

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?

The precondition "The blog must already have a title" is genuinely useful gating information. However, there is no explicit guidance on when to use this versus get_blog_custom_domain or remove_blog_custom_domain; the when-to-use is only implied by the verb "claim".

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

All GoodSender toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources