Skip to main content
Glama

set_status

Updates the status field for a numbered row in a shared issue-tracking Google Sheet so teammates can mark work as in progress or complete within their assigned scope.

Instructions

[쓰기] No.{no} 의 '상태' 칸을 바꾼다(예: 확인중, 完). 사용자가 맡긴 범위 안에서만 부를 것.

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>",
      "status": "<status>"
    },
    "name": "set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
noYes
statusYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It does disclose the mutation nature via the '[쓰기]' (write) tag and adds an authorization scoping rule, which is real value. However it says nothing about whether the previous status is lost, whether invalid status strings are rejected, or whether the user must confirm before the write — important gaps for an unannotated mutation tool.

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 definition is two short sentences with the write tag and the target resource front-loaded, followed by the constraint. No filler. The only minor inefficiency is that the example values are embedded in the action sentence rather than separated out as a value reference.

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?

The tool is simple (2 required params) and an output schema exists, so return values need not be explained. Still, the description leaves out what entity owns the record, what values status accepts, and what a failed write looks like — gaps that matter more here because no annotations supply a safety profile.

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. It does partially: it maps 'No.{no}' to the target record and '상태' to the status column, and gives example values (확인중, 完). But it never clarifies whether 'status' accepts arbitrary free-form strings or a constrained set — the mixed Hangul/Hanja examples actually suggest free-form, which an agent cannot act on confidently.

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 states a specific verb ('바꾼다' / change) and a specific resource ('상태' column of record No.{no}), with concrete example values (확인중, 完). It is clearly distinguishable from all siblings (add_issue, append_comment, get_issue, list_issues, list_tabs, read_tab), none of which mutate a status field. It falls short of 5 only because the owning entity of 'No.{no}' (issue? tab?) is never named.

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?

The only guidance is the authorization constraint '사용자가 맡긴 범위 안에서만 부를 것' (call only within the scope entrusted by the user), which is genuinely useful. There is no when-to-use versus alternative guidance, no statement about prerequisites such as confirming the target record exists, and no indication of which status values are legal versus merely illustrative.

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