Skip to main content
Glama

Builderlog

매일 자동으로 돌리기(팩 설치 안내)

pack_install
Read-only

블로그 팩을 사용자 컴퓨터(Claude 데스크톱 앱의 Code)에 설치하는 순서와 붙여 넣을 한 줄을 알려 줘요. 로그인했다면 내 이용권 팩 목록도 보여 줘요. 설치·결제를 대신 하지 않아요.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the bar is lower, yet the description still adds useful behavior: the response is a procedure plus a paste-ready one-liner, the output expands conditionally on login state, and it explicitly does not install or take payment ('설치·결제를 대신 하지 않아요'). That last line preempts the most likely agent misread of a tool named pack_install. It stops short of describing what happens when the user is not logged in or how the snippet is scoped to an app version.

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, each carrying distinct information: what is returned, the login-conditional extra output, and the non-action boundary. The key clarification (it only tells you how, it does not install) is placed where it will be read, and there is no filler.

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 zero-parameter, read-only guidance tool with no output schema, the description covers the essentials: return content, the login-conditional branch, and the explicit non-mutation boundary. The only soft spot is the undefined behavior when the user is logged out, which an agent would have to discover by calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the description purports to describe inputs, so no misleading inference is created.

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 specific verb-and-resource pair ('블로그 팩을 ... 설치하는 순서와 붙여 넣을 한 줄을 알려 줘요') and makes explicit that this returns instructions rather than performing an install. That distinction matters because the tool name 'pack_install' could otherwise be read as an executor. It does not explicitly contrast itself with any sibling, and the title's framing ('매일 자동으로 돌리기') sits slightly at odds with the description's narrower 'install guide' framing.

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: an agent can infer this is for when a user wants to set up a blog pack on their own machine. There is a genuine conditional ('로그인했다면 내 이용권 팩 목록도 보여 줘요'), but no statement of when to call this versus other setup-type siblings, and no prerequisites such as account state beyond the login aside.

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