Skip to main content
Glama

OpenCurrent

워크플로 훑어보기

list_workflows
Read-onlyIdempotent

검색어 없이 용도·주제·도구·상태·점수로 워크플로 목록을 훑을 때 사용(예: 'Claude Code를 쓰는 검증된 워크플로를 점수순으로'). 축별 개수(facets)도 함께 와서 어떤 조건으로 더 좁힐지 선택 가능. 결과가 많으면 nextCursor로 이어 받을 것.

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

Input Schema

NameRequiredDescriptionDefault
goalNo하려는 일 id로 좁히기 (list_goals의 id = category). 모르는 값이면 좁히지 않음
kindNo종류로 좁히기: prompt(바로 쓰는 프롬프트, 결과 예시 포함), workflow(여러 단계)
sortNo기본 popular(인기순: 근거 있는 점수 → 쓰인 횟수 → 최근)
toolNo이 도구를 쓰는 것만
limitNo기본 20, 최대 50
topicNo주제로 좁히기 (주 용도 포함): dev(개발), research(리서치·학습), writing(글쓰기), data(데이터 분석), ops(업무 자동화), product(기획·디자인), video(영상 제작), image(이미지·그래픽), audio(음악·오디오), marketing(마케팅·콘텐츠), sales(영업), support(고객 지원), education(교육·강의), meeting(회의·협업), translation(번역·외국어), legal(법률·계약), finance(재무·회계), hr(채용·인사), personal(개인 생산성)
cursorNo
domainNo업무 분야로 좁히기 (D100)
statusNo
categoryNo
minScoreNo
capabilityNo필요한 기능으로 좁히기 (D100)

Output Schema

NameRequiredDescriptionDefault
facetsYes
matchedYes
resultsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the extra credit goes to the description's disclosure that the response includes per-axis facet counts and a nextCursor for continuation. That is real behavior an agent would otherwise only discover after calling, and it goes beyond what the annotations declare.

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?

Three sentences, front-loaded with the usage condition, then the facet payoff, then the pagination instruction. Every sentence carries distinct information and nothing is repeated from the title or schema.

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 12 optional parameters and an output schema present, the description supplies the two things the structured fields don't: that facets come back for narrowing, and that results paginate via nextCursor. It is slightly thin on how multiple filters combine, but the core calling decision is fully covered.

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 67%, a middle band where the schema does most of the work. The description groups the available filters as 용도·주제·도구·상태·점수, which mirrors the goal/topic/tool/status/minScore parameters but adds no format, combination, or precedence semantics beyond the schema text.

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 states a specific verb and resource (browse a workflow list) and immediately scopes it with '검색어 없이' (without a search term), which distinguishes it from the search_workflows sibling. The concrete example ("Claude Code를 쓰는 검증된 워크플로를 점수순으로") shows exactly what a call looks like.

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 gives an explicit when-to-use condition (browsing without a query) and explains how to act on the response: pick a narrowing condition from the facet counts, and follow nextCursor when results are numerous. It stops short of naming what to use instead when the user does have a keyword, though the '검색어 없이' qualifier implies that boundary.

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