Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Get Blog Settings

get_blog
Read-onlyIdempotent

Get publication settings for the API key's workspace (title, description, sender, theme, custom domain) and the live design state. Design.IsDefault true means the blog still renders the stock design every workspace starts from; the blog_design_* tools create a custom one. Theme says nothing about it.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
ThemeYesTheme key. Says nothing about the Liquid design; see Design.
TitleYesVisible public blog title and the fallback search/social title when SEO Title is empty.
DesignYes
SEOTitleYesStored publication-wide search/social title override for the blog homepage and archive, or empty when the current public Title supplies the fallback.
SenderNameYesNewsletter From display name if set.
DescriptionYesVisible public blog description and the fallback search/social description when SEO Description is empty.
CustomDomainYesCustom blog hostname if set.
SendingDomainYesNewsletter From domain if set.
TitleIsCustomYesTrue when a real title is stored.
WorkspaceNameYesWorkspace name placeholder.
MailingAddressYesFooter mailing address if set.
SEODescriptionYesStored publication-wide search/social description override for the blog homepage and archive, or empty when the current public Description supplies the fallback.
SenderLocalPartYesNewsletter mailbox local-part if set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so safety is handled. The description adds genuinely non-obvious interpretive behavior — what Design.IsDefault=true actually means and the trap that Theme 'says nothing about it' — which is exactly the kind of context annotations cannot convey. It omits auth scope and whether a missing blog errors out, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the returned surface front-loaded and the interpretive caveat after it; every sentence carries information. The final clause ('Theme says nothing about it') is slightly clipped and relies on the reader connecting it back to the design state, but it is not wasted text.

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?

An output schema exists, so return values need not be spelled out, yet the description still explains the one field most likely to be misread (Design.IsDefault). For a zero-param read tool with rich annotations this is close to complete; only the relationship to update_blog as the write counterpart is left implicit.

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 takes zero parameters, so per the baseline this scores 4; there is nothing for the description to clarify and it correctly spends no words on inputs.

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?

States a specific verb+resource ('Get publication settings for the API key's workspace') and enumerates the fields returned (title, description, sender, theme, custom domain) plus the live design state. It is clearly distinct from update_blog (mutation) and the blog_design_* family (design mutation) without requiring schema inspection.

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?

Explicitly routes the agent: the design state comes from this tool, while 'the blog_design_* tools create a custom one', and it warns that Theme is not a proxy for a custom design. No exclusion vs. update_blog or get_blog_custom_domain is stated, so it stops short of a full when/when-not map.

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