Skip to main content
Glama

list_issues

Retrieve issue rows from a shared Google Sheet, filtered by status such as open, all, or a specific value, and optionally truncate long text fields to a set character limit.

Instructions

문제점 목록. status: 'open'(끝난 상태 제외, 기본) / 'all' / 특정 상태값(예: '재등록'). 긴 칸은 text_limit 글자에서 자른다(0 이면 자르지 않음).

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

Input Schema

NameRequiredDescriptionDefault
statusNoopen
text_limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the important default filtering behavior (finished states excluded) and that long fields are truncated, which materially affects what the agent receives. It omits ordering, pagination, and volume expectations for a list operation, so disclosure is partial but not absent.

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?

Two sentences, front-loaded with the resource and then the two parameters in schema order; no filler, and each clause carries usable information. The parenthetical defaults are efficient rather than redundant.

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?

An output schema exists, so return values need not be described, and both input parameters are meaningfully annotated despite zero schema coverage. What remains thin is the purpose statement and any note on result volume or ordering for a list call.

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 must compensate, and it does: status is explained as 'open' (excluding finished states, the default) / 'all' / a specific status value, and text_limit is explained as a truncation length where 0 disables truncation. Both parameters gain meaning that the bare schema defaults do not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"문제점 목록" is essentially a noun-phrase restatement of the tool name list_issues; it never names a verb, scope, or how it differs from siblings such as get_issue or list_tabs. The real information density sits in the parameter notes rather than in a purpose statement.

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?

It implies usage through the default ('open' = finished states excluded) so an agent can infer that calling with no arguments yields active issues only. However, no alternative is ever named and there is no explicit when-to-use-this-vs-get_issue guidance.

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