Skip to main content
Glama

Builderlog

블로그 글감 추천

blog_ideas
Read-only

이번 달 일정(세금·제도·계절)과 사용자가 말한 블로그 분야·주제로 글감 3~5개를 만들어요. 글감마다 글 종류, 이유, 확인할 곳(네이버 검색·공식 사이트 주소)을 붙여요. 검색량·순위는 알지 못하고, 입력을 저장하지 않아요.

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_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo글 종류: general 일반 정보 · howto 사용법·설정 · money 돈·세금·계산 · it IT·제품 가격 · entertainment 방송·연예 리뷰 · review 제품 후기(직접 써 본 것) · visit 방문 후기(맛집·장소, 직접 가 본 곳)
countNo글감 수(3~5, 기본 3)
fieldNo내 블로그 분야·주제(예: 육아, 재테크, IT 기기, 살림). 모르면 비워요

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only status and closed-world scope, and the description adds genuinely new behavioral facts: each idea carries a post type, a reason, and verification sources (Naver search, official site URLs), plus an explicit capability limit (no search volume or ranking data) and a privacy guarantee (inputs are not stored). The only missing piece is what the response envelope looks like, which is minor given no output schema exists.

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 what is produced and from which inputs, followed by output shape, then limits. Every clause carries information — nothing is repeated from the title or wasted on filler.

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?

For a three-parameter, read-only, non-destructive tool with no output schema, the description supplies the missing return-shape information (per-idea type, reason, verification sources), states the capability boundary, and confirms no input retention. An agent has everything needed to select and call it correctly.

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%, with the enum for kind fully enumerated and defaults documented for count and field. The description reinforces that ideas are derived from the user's stated field and that output count is 3-5, but adds no new semantics for individual parameters beyond what the schema already says. Baseline 3 applies when the schema does the heavy lifting.

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 + resource + scope: builds 3-5 blog post ideas from this month's calendar (tax/policy/season) plus the user's stated field or topic. It also distinguishes itself from keyword-oriented siblings by declaring it does not know search volume or rankings, so an agent can tell it apart from blog_keyword_volume without opening any 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?

The description establishes clear usage context (when the user wants fresh post ideas grounded in the current month and their niche) and includes a negative scope statement that rules out the keyword-research use case. It stops short of explicitly naming an alternative tool to use instead, so it falls just below the top mark.

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