Skip to main content
Glama

Builderlog

체험단·협찬 협업 글·제안 메일 틀

blog_collab_draft
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": {
      "kind": "<kind>"
    },
    "name": "blog_collab_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesexperience_apply 체험단 신청 글 · sponsor_pitch 협찬 제안 메일 · disclosure_note 협찬 글 맨 앞 표기 문구
brandNo업체·브랜드 이름(선택)
productNo제품 이름(선택)
my_statsNo직접 확인한 내 숫자(선택)
providedNo받은 것(제품·원고료 등, 선택)
blog_introNo내 블로그 소개 한 줄(선택)

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, but the description adds genuinely new behavior that the annotations do not cover: unprovided fields become `{중괄호}` placeholders, performance statistics are not invented, and the tool does not send mail, publish posts, or save anything. The no-fabrication and placeholder conventions are exactly the kind of output-behavior context an agent needs. It stops short of describing output length or structure, so not a 5.

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 deliverable and followed by fill behavior and safety constraints. No filler, no repetition of the title, and each sentence carries a distinct obligation.

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?

For a read-only, no-output-schema template generator with full schema coverage, the description covers what it produces, how gaps are handled, and what it will not do. The only mild gap is that it does not describe the shape or approximate size of the returned template, though that is a minor omission for this tool's complexity.

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%, and every parameter, including the `kind` enum, is already documented in the schema, so the baseline is 3. The sentence about filling only user-provided values and leaving blanks as braces adds a modest behavioral cue about the optional parameters, but no meaning beyond what the schema spells out.

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, 틀을 만들어요 (make a template), and lists the three concrete template artifacts: 체험단 신청 글, 협찬 제안 메일, and 협찬 글 맨 앞 표기 문구. These map one-to-one to the `kind` enum values, so an agent can match the request to the tool without opening the schema. No sibling tool in the list does template fill-in for collaboration content, so the purpose is tellable apart.

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 use case is implied by naming the three template types, but the description never states when to choose this tool over something like `blog_brief` or `blog_ai_tone_check`, and it offers no explicit trigger or exclusion. An agent must infer from the enum that this is the drafting-template tool. Adequate but no routing guidance.

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