Skip to main content
Glama

Builderlog

조회가 줄어든 옛 글 찾기

blog_decay_check
Read-only

사용자가 붙여 넣은 글별 일별 조회 표(쉼표·탭 구분, 열: 날짜·제목·조회수)에서 최근 7일 조회가 직전 7일보다 20% 이상 줄어든 글을 찾고 손볼 방향(보강·합치기·방치 검토)을 알려요. 블로그 통계를 읽지 않고, 줄어든 이유는 판단하지 않아요. 저장하지 않아요.

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": {
      "table": "<table>"
    },
    "name": "blog_decay_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
blogNo표에 블로그가 여러 곳일 때 볼 블로그 이름(선택)
tableYes글별 일별 조회 표(첫 줄은 열 이름: 날짜,제목,조회수). 스프레드시트에서 복사한 탭 표도 돼요. 최근 14일 이상, 글 10편 이상일 때 판단해요
todayNo기준일 YYYY-MM-DD(선택, 기본은 표의 마지막 날짜)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 adds real behavioral content beyond them: the 7-day-versus-7-day comparison window, the 20% threshold, the three recommendation categories, and explicit negatives (does not read blog stats, does not judge the cause of the decline, does not save). The remaining gap is what the response actually looks like structurally, which is left implicit.

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 with the core rule and scope front-loaded, followed by the negative boundaries. No filler, and each clause contributes either a rule, a scope limit, or the output shape.

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?

With no output schema, the description does carry the burden of explaining the return value, and it names the recommendation categories, which is the key part. Combined with the schema's input-format detail and the read-only annotations, an agent has enough to call it correctly; only the precise response structure remains unstated.

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%, so all three parameters (table, blog, today) are already documented with format and defaults. The description restates the table's comma/tab separation and date-title-views columns, which duplicates rather than extends the schema, and it never mentions the optional blog or today parameters. Baseline 3 applies when the schema carries the semantics.

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 and resource (find posts whose last-7-day views dropped 20%+ versus the prior 7 days in a pasted per-post daily table) and names the concrete output (a fix direction: reinforce / merge / consider dropping). It also draws an explicit boundary against stats-reading siblings with '블로그 통계를 읽지 않고', so an agent can tell it apart from blog_check without opening the 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?

Usage context is clear: the tool operates on a user-pasted table, not live blog statistics, and the schema-level precondition of 14+ days and 10+ posts further constrains when it applies. It stops short of explicitly routing the agent ('if you need live stats, use X instead'), so it is clear context rather than a full when/when-not/alternative statement.

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