Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Get Blog Custom Domain

get_blog_custom_domain
Read-onlyIdempotent

Get custom-domain claim status and DNS targets for the workspace blog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_blog_custom_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context about what information is returned (claim status and DNS targets), which goes beyond the annotations, though it does not mention auth or rate-limit behavior.

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 a single, front-loaded sentence with no redundant words. Every element — verb, resource, and returned data — earns its place.

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?

Given zero parameters, full annotations, and an output schema, the description provides sufficient context about what the tool does and what it returns. It could be slightly more complete by noting prerequisites such as whether a domain must already be claimed, but the core purpose is fully conveyed.

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

Parameters4/5

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

The tool has zero parameters and schema description coverage is 100%, so there is no parameter semantics to explain. Baseline for zero parameters is 4.

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 states a specific verb ('Get') and a precise resource: custom-domain claim status and DNS targets for the workspace blog. It is clear enough to distinguish from mutation siblings like connect_blog_domain and remove_blog_custom_domain, but it does not explicitly reference those alternatives.

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 by the description: call it when you need the domain claim status or DNS targets. However, it offers no explicit when-to-use guidance, no exclusions, and no contrast with siblings like connect_blog_domain or check_sender_domain_stats.

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