Skip to main content
Glama

Builderlog

블로그 표지 만들기

blog_cover
Read-only

표지 문구로 1080×1080 표지 그림을 보여 주는 화면 주소를 만들어요. 사용자가 주소를 열면 미리 보고 PNG 로 저장해요. 그림은 사용자 브라우저에서 그려지고 이 서버에 남지 않아요. 큰 글자 1줄(14자 안팎)·강조 1줄·작은 꼬리표.

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": {
      "line1": "<line1>"
    },
    "name": "blog_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo왼쪽 위 작은 꼬리표(선택, 예: 2026 기준)
line1Yes큰 글자 첫 줄
line2No빨간 강조 줄(선택)
styleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; on top of that, the description adds genuinely non-obvious behavior: rendering happens in the user's browser and nothing is persisted on the server. It does not cover rate limits or auth, but neither is relevant to a client-side render, so this is close to complete for the operation.

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 output (a URL for a 1080×1080 cover), followed by user flow, privacy behavior, and layout constraints. Every sentence carries information and none repeats the name or title.

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?

With no output schema, the description carries the return value itself and does so clearly (an address that displays the cover). Combined with annotations and the client-side rendering note, an agent has enough to invoke it correctly; only the effect of the style enum is left unexplained.

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?

Schema coverage is 75%, so the schema documents most fields, but the description adds real meaning the schema lacks: the ~14-character guideline for the big line and how the three text slots (label, big line, emphasis line) compose the cover. The one gap is the style enum (light/dark), which has no description in the schema and no explanation in the description either.

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?

The description names a specific verb and artifact: it produces a screen URL that renders a 1080×1080 cover image from the supplied cover text. That verb+resource pairing is unambiguous and does not overlap with any sibling tool, which are all checks, analyses, or drafts.

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?

The description explains the downstream flow (the user opens the address, previews, and saves a PNG), which implies usage, but it never states when to reach for this tool versus another or when not to use it. There is no explicit comparison or exclusion against the many sibling blog_* tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources