Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Get blog design contents

blog_design_get_latest_checkpoint
Read-onlyIdempotent

Get the latest checkpoint of a design.

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

Input Schema

NameRequiredDescriptionDefault
DesignIDYesDesign UUID whose latest checkpoint to read.

Output Schema

NameRequiredDescriptionDefault
LatestCheckpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and closed-world, so the safety profile is fully covered elsewhere and the bar is low. The description adds essentially nothing beyond annotations and title: it does not say what happens when no checkpoint exists, whether the latest checkpoint could be a draft/unpublished state, or what a caller gains over listing checkpoints.

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?

One short, front-loaded sentence with no waste. It is arguably over-lean for a tool with three similarly named checkpoint siblings, but nothing in it is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explained, and the single required param is fully specified. What is missing is the relational context an agent needs among the checkpoint family (list vs. get-latest vs. restore) and any failure-mode behavior, which matters for a read tool in a mutation-heavy cluster.

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% and the single DesignID parameter is documented with UUID format and a regex pattern, so the schema does the heavy lifting. The description contributes no additional meaning about the parameter, which is the correct baseline when coverage is complete.

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?

Specific verb ('Get') and resource ('the latest checkpoint of a design') make the operation unambiguous. However, it does not distinguish itself from the close sibling blog_design_checkpoint_list, so an agent cannot tell from the description alone which of the two to reach for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this instead of blog_design_checkpoint_list, blog_design_checkpoint_restore, or blog_design_list. The word 'latest' hints that no checkpoint ID is needed, but the agent must infer that, and no preconditions or exclusions are given.

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