Skip to main content
Glama

Builderlog

내 키 연결 안내

builderlog_setup
Read-only

빌더로그 도구에 붙일 수 있는 내 API 키(네이버 검색광고·네이버 검색·AI 이미지) 목록과 키별 발급 3단계, 키 없이 되는 것과 키를 붙이면 더 되는 것을 보여 줘요. 로그인했다면 내 연결 상태와 다음에 할 일 1개도 보여 줘요. 키를 받거나 저장하지 않아요(키는 등록 화면이나 내 컴퓨터에만 넣어요).

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": "builderlog_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo자세히 볼 키(선택): searchad 네이버 검색광고 · naver_search 네이버 검색 · image_ai AI 이미지 · search_console 서치 콘솔

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description earns credit mainly for the disclosure that the tool does not receive or store keys ("키를 받거나 저장하지 않아요"), which is real behavioral context a schema cannot convey, plus the conditional login-state branch. It does not say how the login state is detected, what an anonymous caller sees, or how next-action is chosen, so it goes beyond annotations but not richly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the primary payload before the logged-in branch and the no-storage caveat. The parenthetical explaining where keys actually go earns its place; nothing is redundant enough to trim meaningfully.

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 single-optional-parameter, read-only, no-output-schema tool, the description covers what is returned, the conditional behavior, and the key-safety guarantee. Remaining gaps (exact shape of the returned list, what the next-action item looks like) are minor and arguably out of scope without an output schema.

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?

The single optional `key` parameter has 100% schema description coverage with an enumerated, labelled value set, so the schema does the heavy lifting and a baseline 3 applies. The description's mention of per-key issuance steps hints at the detail view but never says that passing a key narrows output to one key, leaving that link implicit.

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 uses a concrete verb ("보여 줘요" / shows) applied to a precisely enumerated payload: the list of API keys usable with builderlog tools (Naver search ad, Naver search, AI image), the 3-step issuance per key, and what works with vs. without keys. It also names a second mode (login state → connection status plus one next action), so an agent can tell this is a setup/guidance tool rather than one of the blog_* generation or check siblings. It stops short of 5 only because the framing sentence is long and the two modes are not visually separated.

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 implied rather than stated: an agent can infer this is the place to look for key issuance steps or connection status, and the description notes the logged-in branch. There is no explicit when-not-to-use guidance and no named alternative among the many blog_* siblings for adjacent questions (e.g., whether a given tool needs a key).

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