Skip to main content
Glama

append_comment

Appends a dated, role-tagged reply as a new line at the end of your own column cell in a shared sheet, preserving existing content so teammates can log status updates without overwriting history.

Instructions

[쓰기] No.{no} 의 내 칸 끝에 "[M/D 역할] text" 를 새 줄로 덧붙인다(기존 내용은 지우지 않는다). date 를 비우면 오늘 M/D. 공유 문서를 바꾸므로 사용자가 맡긴 범위 안에서만 부를 것.

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": {
      "no": "<no>",
      "text": "<text>"
    },
    "name": "append_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
noYes
dateNo
textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations at all, the description carries full burden and does real work: it declares the write nature, states '기존 내용은 지우지 않는다' (non-destructive append), and warns that a shared document is mutated. It does not cover permission requirements, concurrent writers, or what happens if the target No. does not exist.

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?

Two dense sentences with the [Write] tag front-loaded, then the operation, then the constraint. Every clause carries information; the only slight cost is the terse template notation that the reader must decode.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the write/scope profile is covered. But for a mutation tool with zero annotations, two gaps remain: '내 칸' (my cell) presupposes a caller identity the agent may not have, and the exact format contract for the appended line is unresolved.

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 0%, so the description must compensate, and it partially does: 'No.{no}' identifies no as the target cell, and 'date 를 비우면 오늘 M/D' explains the empty-string default. However, it never clarifies whether the '[M/D 역할] text' prefix is generated by the tool or must be included by the caller in text, which leaves the text parameter ambiguous.

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 gives a concrete verb and resource in the bracket tag '[쓰기]', then states exactly what is appended ('[M/D 역할] text' as a new line) and where (the end of my cell in No.{no}). It is enough to tell append_comment from the read-oriented siblings (read_tab, list_tabs) 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?

'date 를 비우면 오늘 M/D' gives a conditional for the default case, and '공유 문서를 바꾸므로 사용자가 맡긴 범위 안에서만 부를 것' adds an explicit scope restriction on when to call it. There is no direct contrast with a sibling tool, so it does not reach the top level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.