Skip to main content
Glama

Builderlog

블로그 글 설계

blog_brief
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": {
      "topic": "<topic>"
    },
    "name": "blog_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo글 종류: general 일반 정보 · howto 사용법·설정 · money 돈·세금·계산 · it IT·제품 가격 · entertainment 방송·연예 리뷰 · review 제품 후기(직접 써 본 것) · visit 방문 후기(맛집·장소, 직접 가 본 곳)
topicYes쓸 주제 한 줄
keywordNo검색 키워드(제목 앞 12자 안에 넣을 말)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 stays consistent while adding two useful facts: it produces a plan rather than prose and it does not persist the input. Since there is no output schema, spelling out what kind of result comes back is genuinely valuable, though it stops short of describing the exact return shape.

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?

Two short sentences, no filler, with the produced artifact and its components front-loaded and the scope limits second. Every clause carries information.

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?

A simple read-only, three-parameter tool with full schema coverage and no output schema; the description covers purpose, non-persistence, and the fact that no draft text is generated. The only gap is routing guidance relative to sibling tools.

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%, so all three parameters are already documented, including the enum values for kind and the 12-character title rule for keyword. The description only restates the three inputs as the basis for the design sheet, adding no format or constraint detail beyond the schema; baseline 3 applies.

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?

The description gives a specific verb and resource ('글 설계표...를 만들어요') and enumerates the sheet's contents (title rules and frame, subheading order, evidence list, tone rules), so the agent knows exactly what artifact it gets. It does not name or contrast any sibling such as blog_ideas or blog_repurpose_plan, which keeps it at 4 rather than 5.

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?

Usage is only implied: the mention of '쓰기 전에 열어 볼 근거 목록' signals this is a pre-writing step. The negatives ('글 본문은 쓰지 않고') carve out scope but do not tell the agent when to pick this over the many sibling check/idea 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