Skip to main content
Glama

add_issue

Appends a new dated issue row to a shared Google Sheet, registering problems or teammate questions in the correct mode, model, and note fields.

Instructions

[쓰기] 표 맨 아래에 새 행(다음 번호, 오늘 날짜). 문제 등록이나 상대에게 묻는 질문에 쓴다. mode 는 '모드'(분류) 칸, problem 은 '문제점' 칸, model 은 '모델' 칸(비우면 역할 이름), note 는 내 칸. 사용자가 맡긴 범위 안에서만 부를 것.

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": {
      "mode": "<mode>",
      "problem": "<problem>"
    },
    "name": "add_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
noteNo
modelNo
statusNo등록
problemYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does flag this as a write operation ('[쓰기]') that appends rather than overwrites and auto-generates the sequence number and date. It says nothing about permissions, duplicate handling, side effects on existing rows, or failure modes, which matters for a mutation tool with zero annotation coverage.

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?

The write tag and the core action come first, followed by usage, then per-parameter column mappings, then the scope constraint — a logical front-loaded order with no filler. Sentences are short and each carries information, though the parameter list reads as terse fragments.

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 five-parameter mutation tool with no annotations, the description covers the essential behavior (append semantics, auto-filled fields, column mapping, delegation boundary), and the output schema means return values need no explanation. The undocumented 'status' parameter is the one substantive omission.

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?

Schema coverage is 0%, so the description does the heavy lifting: it maps mode, problem, model, and note onto specific spreadsheet columns and even discloses fallback behavior for model (empty → role name). It never mentions the 'status' parameter (default '등록'), leaving one of five parameters undocumented.

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 gives a concrete verb and target: it appends a new row at the bottom of the table, auto-filling the next number and today's date, and covers two use cases (registering an issue or posing a question). That distinguishes it from read-side siblings like get_issue or list_issues, though it does not explicitly separate itself from append_comment.

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?

It states the triggering situations ('문제 등록이나 상대에게 묻는 질문') and adds a clear boundary constraint to call it only within the scope the user delegated. It does not name a sibling alternative or state when not to use it, so it stops short of explicit routing guidance.

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