Skip to main content
Glama

Builderlog

글 1편 재가공 지시표(스레드·카드뉴스·숏츠)

blog_repurpose_plan
Read-only

완성한 블로그 글을 스레드·인스타 카드뉴스·숏츠 대본으로 줄일 때 쓰는 지시표를 만들어요. 원문 소제목 순서대로 배치하고 원문에 있는 숫자만 근거로 뽑아요. 새 글은 쓰지 않고, 올리지 않고, 저장하지 않아요.

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": {
      "body": "<body>"
    },
    "name": "blog_repurpose_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes완성한 블로그 글 전체(마크다운)
targetNothread 스레드 · cardnews 인스타 카드뉴스 · shorts 숏츠 대본(기본 thread)
audienceNo읽는 사람 한 줄(선택)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, and the description adds meaningful behavior on top: it does not write new text, does not publish, and does not persist anything ('저장하지 않아요'). It also discloses the transformation rules (source subtitle order, numbers only from the source), though it says nothing about length limits or how large an input post can be.

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 and its target formats, then the transformation rules, then the non-actions. No filler or repetition of the 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 does sketch what the plan contains (subtitle ordering, source-grounded numbers) and confirms it is read-only and non-persistent, which covers what an agent needs before calling. A brief note on the shape or size of the returned instruction sheet would close the remaining gap.

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 description coverage is 100%, including the target enum values with their Korean meanings, so the schema already carries the parameter burden. The description adds constraints on the output (subtitle order, source-only numbers) but nothing extra about body, target, or audience semantics, which is the expected baseline here.

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?

States a specific verb and artifact ('지시표를 만들어요') plus the three concrete output formats the finished post is condensed into (스레드·인스타 카드뉴스·숏츠 대본), so the agent can tell it apart from drafting tools. It stops short of naming a sibling alternative explicitly, so it is clear but not fully differentiating on its own.

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?

The trigger condition is clear: use it when you already have a finished blog post to shrink into other formats ('완성한 블로그 글을 … 줄일 때'). The boundary '새 글은 쓰지 않고' implicitly excludes it from drafting work, but no explicit alternative tool is named for the case where no finished post exists.

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