Skip to main content
Glama

OpenCurrent

하려는 일별 묶음 보기

list_goals
Read-onlyIdempotent

사용자가 하려는 일에 맞는 방법을 고를 때 먼저 사용. 묶음은 하려는 일 여섯(개발·리서치·학습·글쓰기·데이터 분석·업무 자동화·기획·디자인) 가운데 글이 있는 것, 묶음마다 이름(title)과 그 안의 워크플로가 인기순으로 옴(근거 있는 점수 → 쓰인 횟수 → 최근). 워크플로마다 근거 한 줄(proof)이 있어 본문을 받기 전에 고를 수 있음. 고른 것은 get_workflow로 받을 것.

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_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo묶음마다 받을 워크플로 수, 기본 5

Output Schema

NameRequiredDescriptionDefault
noteYes
goalsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false. The description adds genuinely useful behavior beyond that: only bundles with content are returned, ordering is justified ranking (evidence score → usage count → recency), and each workflow carries a one-line proof so selection can happen before fetching the body. It stops short of stating size bounds or that results are stable across calls; the sorting detail is the main value add.

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?

Front-loaded with the imperative ('사용자가 하려는 일에 맞는 방법을 고를 때 먼저 사용') so the agent hits the when-to-use rule first, and each following clause covers result shape, ordering, and next step. The long parenthetical ranking explanation is dense and the six-vs-eight enumeration error costs some polish.

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 an output schema present and annotations covering the safety profile, the description needn't explain return values, and it correctly focuses on selection and follow-through. Nothing critical is missing for calling it correctly, though a note on the default page size or on what an empty bundle list means would round it out.

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?

The single parameter `top` has 100% schema description coverage ('묶음마다 받을 워크플로 수, 기본 5', max 20), so the schema carries the semantics. The description never mentions the parameter, its default, or its upper bound, so it adds nothing here — baseline 3 applies.

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?

States a concrete verb and resource — it lists bundles (묶음) each with a title and its workflows in popularity order — and explicitly routes the agent to get_workflow for anything it picks. The one blemish is internal: it says there are six kinds of intended work (하려는 일 여섯) and then enumerates eight, which slightly muddies what the result set contains.

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?

Gives a clear sequencing rule ('먼저 사용' — use this first when choosing an approach for the user's intended task) and names the follow-on tool for the chosen item (get_workflow). It does not state any exclusion, e.g. skip this when a specific workflow name is already known and search_workflows would be faster.

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