Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Activate a blog design

blog_design_activate
DestructiveIdempotent

Make this saved design the live blog design. Readers see it at once. The workspace keeps one active design. An empty design is rejected. This changes the public site immediately. The previous design stays in the list, so going back is activating it again (the stock one is flagged IsDefault in 'blog_design_list').

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": {
      "DesignID": "<DesignID>"
    },
    "name": "blog_design_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
DesignIDYesSaved design to make the live blog design.

Output Schema

NameRequiredDescriptionDefault
TitleYesOn a local server with action guards on, the pending-confirmation notice while the activation awaits approval.
DesignIDYesID of the design that is now active; null while the activation awaits confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive/idempotent/openWorld, but the description adds genuine behavioral value beyond them: changes are immediately public, an empty design is rejected, only one design is active at a time, and the change is reversible via re-activation. That is exactly the context an agent needs before mutating a live site.

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?

Four short sentences, front-loaded with the core effect ('Readers see it at once') followed by constraints and reversibility. No wasted prose.

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?

An output schema exists so return values need no explanation, annotations cover the safety profile, and the description covers the mutation's side effects, constraints, and reversibility. Nothing an agent needs to call this correctly is missing.

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?

The schema fully documents the single DesignID parameter (100% coverage) including uuid format and a description. The tool description adds no syntax or selection guidance beyond calling it a 'saved design', so the schema does the heavy lifting – baseline 3.

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 and resource ('Make this saved design the live blog design') and immediately clarifies the reader-facing effect. It is clearly distinguishable from siblings like blog_design_save, blog_design_edit, and blog_design_create.

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?

Explains the operating context: one active design per workspace, empty designs are rejected, and the previous design remains available so reverting means re-activating it. It even points to 'blog_design_list' for the stock default. It stops short of explicitly naming which alternative tool to use instead, but the conditions for use are clear.

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