Skip to main content
Glama

OpenCurrent

워크플로 찾기

search_workflows
Read-onlyIdempotent

사용자의 작업을 시작하기 전에, 사람들이 검증한 AI 활용 방법이 있는지 찾을 때 사용. 상황을 문장이나 키워드로 넣으면(한국어 가능) 맞는 워크플로를 관련도순으로 반환. 각 결과의 status로 얼마나 믿을지 판단할 것. 단계 전체는 get_workflow로 받을 것.

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": {
      "query": "<query>"
    },
    "name": "search_workflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo종류로 좁히기: prompt(바로 쓰는 프롬프트, 결과 예시 포함), workflow(여러 단계)
toolNo이 도구를 쓰는 것만 (예: 'Claude Code'). 표기가 조금 달라도 맞춤
limitNo최대 개수, 기본 5
queryYes하려는 일이나 상황. 예: '회의록 정리', 'onboard to a new codebase'
topicNo주제로 좁히기 (주 용도 포함): dev(개발), research(리서치·학습), writing(글쓰기), data(데이터 분석), ops(업무 자동화), product(기획·디자인), video(영상 제작), image(이미지·그래픽), audio(음악·오디오), marketing(마케팅·콘텐츠), sales(영업), support(고객 지원), education(교육·강의), meeting(회의·협업), translation(번역·외국어), legal(법률·계약), finance(재무·회계), hr(채용·인사), personal(개인 생산성)
cursorNo앞 응답의 nextCursor를 넣으면 다음 결과
domainNo업무 분야로 좁히기 (D100): dev(개발), vibe(바이브 코딩), marketing(마케팅), design(디자인), content(콘텐츠·미디어), education(교육), research(연구·리서치), sales(영업·고객 지원), ops(운영·사무), finance(재무·회계), planning(기획·전략), other(기타)
statusNo검증 상태로 좁히기: verified(검증됨), pending(검수 대기), check(확인 필요)
categoryNo용도로 좁히기: dev, research, writing, data, ops, product
minScoreNo평가 점수(0~100)가 이 값 이상인 것만
capabilityNo필요한 기능으로 좁히기 (D100): writing(글쓰기·요약), translate(번역), image(이미지 생성), video(영상 생성), audio(음성·전사), code(코드 작성), data(데이터 분석), search(웹 검색), documents(문서 읽기 (PDF·파일)), integrate(앱 연동·자동화), computer(화면 조작 (브라우저·컴퓨터)), other(기타)

Output Schema

NameRequiredDescriptionDefault
noteYes
totalYes라이브러리 전체 워크플로 수
matchedYes조건에 맞는 수
resultsYes
nextCursorYes더 있으면 다음 요청의 cursor에 넣을 것

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the bar is lower. The description adds genuinely new context: results are ranked by relevance and each result carries a status that should be used to judge trustworthiness, plus a pointer that the step body lives in another tool. It says nothing about pagination or result volume, which cursor/limit in the schema only partly cover.

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?

Four short sentences, each doing distinct work: trigger, input form, output interpretation, and next step. The trigger is front-loaded and there is no redundant restatement of the tool name or schema fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter search tool with a full schema, a complete output schema, and read-only annotations, the description covers everything the agent needs to decide to call it: when, how to phrase the query, how to read the ranked results, and where to go next. Remaining details such as filter combinations and cursor paging are fully documented in the schema.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: the query accepts a full sentence or just keywords and Korean is supported, which affects how the agent should phrase input. It does not mention the filtering parameters (kind, topic, status, minScore), leaving their usage entirely to the schema.

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 concrete verb and resource ('워크플로를 ... 찾을 때', '관련도순으로 반환') and explicitly separates this tool from get_workflow, which retrieves full steps. An agent can distinguish search from retrieval without opening either schema.

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 a clear trigger ('사용자의 작업을 시작하기 전에') and routes follow-up work to get_workflow, so the search-then-fetch flow is obvious. It does not address when to prefer the sibling list_workflows or when filtering by kind/topic is better than a free-text query, so exclusions are incomplete.

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