Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Prepare a blog design image upload URL

blog_design_image_upload_url

Get a short-lived URL for uploading one blog design image (logo or favicon).

PUT the image bytes to UploadURL. The JSON response field url is the stored image URL. blog_design_edit accepts that url as LogoURL, Favicon32URL, or Favicon180URL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
ExpiresAtYesWhen UploadURL stops working. About 5 minutes after this call.
UploadURLYesPUT the raw image bytes here before ExpiresAt. Set Content-Type to image/jpeg, image/png, image/gif, or image/webp. No API key. The URL is only for this workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the non-obvious behavior that this tool does not itself upload anything — the caller must PUT bytes to the returned UploadURL, and the stored URL comes back in the response field url. The 'short-lived' constraint is a useful caveat. It stops short of describing failure modes (expired URL, size/type limits) or auth requirements.

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?

Three short sentences, front-loaded with the purpose, then the required action, then the return value and where it plugs in. Every sentence carries actionable information and none restates the title.

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?

With zero params, full annotation coverage, and an output schema for the response fields, the description supplies exactly the missing piece: the two-step upload protocol and the mapping of the returned url into blog_design_edit fields. Nothing an agent needs to invoke it correctly is absent.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly frames the call as parameterless by describing the flow as a single URL request.

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 (get a short-lived upload URL) and narrows scope to a single blog design image (logo or favicon), which cleanly separates it from the post-image sibling upload_post_image. An agent can tell what it produces without opening the schema.

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?

Gives clear context for use: it is the first step of a two-step flow (obtain URL, then PUT bytes), and it names the downstream consumer (blog_design_edit via LogoURL/Favicon32URL/Favicon180URL). It does not explicitly state when not to use it or name a sibling alternative, so it falls short of a 5.

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