Skip to main content
Glama
603,971 tools. Updated 2026-09-23 17:17

"Slack 메시지에서 태그된 항목 조회 및 요약 방법" matching MCP tools:

  • Tidal current predictions for a CO-OPS current station: max flood and ebb speeds, slack times, and the station's mean flood and ebb bearings. These are forecast predictions from CO-OPS, distinct from noaa_marine_get_current_profile, which returns NDBC observed ocean-current measurements binned by depth. The default MAX_SLACK interval is the practical planning view, showing when currents peak and when slack water occurs, and a 6-minute interval returns the continuous curve for detailed analysis, each row carrying its own flood/ebb/slack sense. A station can publish predictions for several depth bins at different depths: bin selects one, omitting it takes the CO-OPS default of the shallowest bin, and the bin and its depth are echoed on every response — read bins[] on a noaa_marine_find_stations current row for the bins a station actually has. A station whose currents CO-OPS will not predict as discrete events answers with an empty list and its own wording in the notice rather than an error. Both intervals are bounded by response size: a range whose rows fit is returned whole, a longer one returns the leading rows with rows_matched, rows_returned, and next_offset reporting how much matched and which offset reaches the rest, and offset and limit walk whichever series the interval selects. Current station IDs are alphanumeric (e.g. ACT4176), distinct from the numeric tide and water-level IDs, and the date range is limited to 1 year per request — use noaa_marine_find_stations with types=["current"] to obtain a valid current station ID.
    ConnectorNo auth
  • Get your Prowlo account details: organization ID + name, your user ID, email, role, plan, account status, and integration state (connected Slack channels, webhook endpoints). Check `integrations` before setting an Alert destination — `destination.slack` only delivers if Slack is connected, and `destination.webhookIds` must reference the webhook ids listed here. Use this to identify your account when contacting support — quote the organizationId so we can find you quickly. (requires a free Prowlo account — call it to get a signup link)
    ConnectorNo auth
  • Scan text or code for leaked secrets: API keys (AWS, GCP, Azure, OpenAI, Anthropic, Stripe, GitHub, GitLab, Slack, Twilio, SendGrid, HuggingFace), private keys (RSA/EC/PGP), JWTs, database connection strings, Bearer tokens, and Basic auth headers. Returns a list of findings with type, severity, line number, and a redacted preview. Use before committing code, sharing logs, or sending text to an LLM. 100% regex-based, zero network calls.
    ConnectorNo auth
  • 판례/해석례 본문 조회 — 판시사항·판결요지·참조조문(판례) 또는 질의요지·회답·이유(해석례). 응답의 `source_url`은 국가법령정보센터 원문 주소다 — 판례·해석례를 인용할 때는 **이 링크를 함께 제시하라**(감사·보고서에서 근거를 되짚을 수 있어야 한다). **`error:"case_body_unavailable"`이면 `source_url`은 null이고 `existence_verified`는 false다**(2026-09-04). 이건 "본문만 없다"가 아니다 — 우리는 ①본문 미제공(하급심· 국세청 등 타기관 제공)과 ②그런 일련번호가 없음을 **구분하지 못한다**(본문 API 응답이 같다). 그러니 **링크를 만들어 채우지 마라**: law.go.kr 뷰어는 없는 번호에도 200과 빈 페이지를 주므로 열린다는 것이 존재의 증거가 아니다. 이 case_id가 search_cases 결과에서 온 것이면 그 결과의 사건명·사건번호·source_url만 인용하고, 아니면 아무것도 인용하지 말고 search_cases로 다시 찾아라. Args: kind: "prec" | "expc" (search_cases 결과의 kind) case_id: search_cases 결과의 case_id
    ConnectorNo auth
  • 판례/해석례 본문 조회 — 판시사항·판결요지·참조조문(판례) 또는 질의요지·회답·이유(해석례). 응답의 `source_url`은 국가법령정보센터 원문 주소다 — 판례·해석례를 인용할 때는 **이 링크를 함께 제시하라**(감사·보고서에서 근거를 되짚을 수 있어야 한다). **`error:"case_body_unavailable"`이면 `source_url`은 null이고 `existence_verified`는 false다**(2026-09-04). 이건 "본문만 없다"가 아니다 — 우리는 ①본문 미제공(하급심· 국세청 등 타기관 제공)과 ②그런 일련번호가 없음을 **구분하지 못한다**(본문 API 응답이 같다). 그러니 **링크를 만들어 채우지 마라**: law.go.kr 뷰어는 없는 번호에도 200과 빈 페이지를 주므로 열린다는 것이 존재의 증거가 아니다. 이 case_id가 search_cases 결과에서 온 것이면 그 결과의 사건명·사건번호·source_url만 인용하고, 아니면 아무것도 인용하지 말고 search_cases로 다시 찾아라. Args: kind: "prec" | "expc" (search_cases 결과의 kind) case_id: search_cases 결과의 case_id
    ConnectorNo auth
  • Create a cost alert that monitors one or more queries and notifies when a condition fires. New alerts are creator-only (you get Admin). To share, call set_object_permissions with resourceKind "costAlert". MCP is create-only — there is no update_alert; edit in the UI via the returned URL. Accepts the same query config as query (prefer `datePreset` over hand-computed from/to). The firing rule is a single `condition` boolean expression over the query `name`s, e.g. `a > 1000`, `rollingSum(a, 7, DAY) > 50000`, or `(a - timeShift(a, 1, DAY)) / timeShift(a, 1, DAY) > 0.2`. Window math (rollingSum/weekToDateSum/monthToDateSum/timeShift) is evaluated daily in BigQuery, so you do NOT pick an evaluation period — instead set `dedup` to control re-notification frequency (CALENDAR once per WEEK/MONTH, or ROLLING once every N days). The period (`datePreset` or `from`/`to`) defines the preview/look-back window for the underlying queries. Use list_available_destinations for SLACK/TEAMS channel IDs. Returns a URL that you MUST include in your response so the user can view/edit the alert. EXAMPLE: "Alert me on Slack if our production AWS spend exceeds $50k over any 7 days, at most once a week" → { name: "Prod AWS weekly alert", queries: [{ type: "cost", name: "a", metricId: "cost", currency: "USD", filterCel: "cos_provider in [\"AWS\"] && cos_environment in [\"prod\"]" }], datePreset: "TRAILING_90_DAYS", condition: "rollingSum(a, 7, DAY) > 50000", dedup: { kind: "CALENDAR", calendarUnit: "WEEK" }, notificationChannel: "SLACK", slackChannelId: "C01ABC" }
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • 사용자가 직접 입력하는 폼이 아니라, 호출 에이전트가 직전 Den 응답을 활용한 뒤 사용자가 보인 반응(수정 지시/불만/채택/무시)을 대화 종료 전 요약 수준으로 기록하는 릴레이 툴. query_id가 있으면 그대로 전달하고, 없으면 직전 Den 툴에 전달한 question_text만 전달한다. satisfied를 기록하고, 불만족이면 issue_type을 지정하며 comment는 반응 요지만 200자 이내로 요약한다. 채택·긍정은 satisfied=true, 수정 지시·불만·명시적 무시는 satisfied=false와 가장 가까운 issue_type으로 매핑한다. 관찰 가능한 반응이 전혀 없으면 만족 여부를 추측하지 않는다. ★satisfied=true(채택·긍정)이면 comment 에 **den 이 없었으면 무엇을 하려 했는지** 한 마디를 함께 적는다 — "다른 값을 쓰려 했다" · "몰라서 정하지 못하고 있었다" · "다른 출처로 갔어야 했다" 중 사용자가 실제로 말한 것. 이 한 마디만이 'den 을 썼다'와 'den 때문에 달라졌다'를 가른다. ★★사용자가 말하지 않았으면 **비워 둔다.** 추측해 지어내지 않는다 — 없는 것을 적는 편이 안 적는 것보다 나쁘다. ★★★그렇다고 comment 를 통째로 생략하지는 않는다. satisfied=true 면 **무엇을 채택했는지** 한 줄은 항상 적는다(어느 값·조문·판단을 그대로 썼는가). 비워 두는 것은 반사실 한 마디뿐이다 — 요지까지 비면 그 만족은 기록에 남아도 쓸 수 없다. → 이 도구는 **질의가 아니다** — 답을 찾으려면 k_snippets·answer_why 를 쓴다. 사용자 대화 원문은 전송하지 않는다. 만족/불만족과 사유는 다음 날 그래프 보완에 반영된다.
    ConnectorNo auth
  • Set how loudly the Coderbuds agent speaks to this team — the single control over whether it acts at all. "off" = silent, Coderbuds still measures but never posts. "preview" = record recommendations in Coderbuds without performing or sending them. "quiet" = weekly pulse only, no nudges. "public" = acts in the open, nudges go to the team channel and never to DMs. "direct" = may message engineers directly. There are no per-capability settings: an individual act that needs a human still asks for approval in Slack regardless of posture. Requires team admin permissions; use get-agent-activity-tool to see the current posture and activity.
    ConnectorOAuth
  • Connect an account that links with a KEY rather than a sign-in screen, from here, with no browser: Stripe, ChatGPT Ads, Apple Ads, Bluesky, Telegram, Bing Webmaster Tools, PostHog, Mixpanel, Amplitude, Slack, Discord, Webhook. Pass provider and fields in that provider's own field names (listed below, * = required). The key is checked live with the provider before anything is saved, exactly as the app's Connectors page checks it, and the reply is read back from the saved connection. OFFER BOTH WAYS AND LET THE USER CHOOSE: a key pasted into this chat stays in this conversation's history, while pasting it in the app (Workspace > Connectors, or the one-click link https://app.hermoso.ai/?connect=<provider>) keeps it out of the chat. Hermoso never repeats a submitted key back. An account that connects through the provider's own sign-in screen (OAuth) cannot be connected here: this answers with the link to hand the user instead. Apple Ads with no key material first generates a signing key pair and returns the public key to register with Apple plus a setupToken to send back. Fields: stripe {apiKey*} · openai_ads {apiKey*} · apple_ads {clientId, teamId, keyId, privateKey, setupToken, orgId} · bluesky {identifier*, appPassword*, pds} · telegram {token*} · bing_webmaster {apiKey*} · posthog {apiKey*, region, host, projectId} · mixpanel {username*, secret*, projectId*, region, workspaceId} · amplitude {apiKey*, secretKey*, region, host} · slack {webhookUrl*} · discord {webhookUrl*} · webhook {webhookUrl*}.
    ConnectorNo auth
  • <summary>Which integrations the account has connected, keyed by the same integration_id you pass to get_tool_connect_url (gmail, outlook, linkedin, slack, googlesheets, salesforce, notion, ...). Call this before telling a user an integration is unavailable, or before minting a connect link for one they say is already connected — it may already be active.</summary> <returns> <description>A dict mapping each integration_id to its connection status; read one with result[integration_id]['connected']. Some entries carry extra detail — linkedin, google_calendar, and fathom include needs_reconnect (connected, but the auth broke and the user must re-link); email and linkedin include the connected account email. A missing key means that integration wasn't checked, not that it's disconnected. The shared_calendars key is a list of shared-calendar rows, not a connection-status entry. The slack entry carries two independent flags: 'connected' is the workspace bot link that delivers Sliq's notifications, and 'slack_mcp_connected' gates only your Slack MCP tools in chat — judge notification delivery by 'connected' alone.</description> </returns>
    ConnectorOAuth
  • List the authenticated third-party accounts the caller can use — their own, plus anything explicitly shared with them or their teams. A connection with NO shares is private to its owner and is never listed for anyone else, whatever permission they hold — this cannot answer "what has Priya connected" and must not be reported as if it could; only its owner can. There is no org-wide listing: an org owner or admin sees exactly this same set, never every connection in the organization, whatever permission they hold. A connection is one account of one connector with a credential held in the vault; this is what "are we connected to Slack" means. Each row carries a `conn_…` id, name, connector_slug, `owner_user_id` with an `owner`: { id, name, email } beside it — say who owns a shared connection by name, never by id — and status: "active" is usable, "pending" means nobody ever finished the provider login, "needs_reauth" means it broke and connection.reconnect is the repair. Every row also carries `access_summary`, a BOUNDED who-else-can-reach-it rollup — { org_level, team_count, user_count, total, preview } — never a full grant list however many grants exist, so answer from its counts ("shared with 3 people and 1 team") and send the user to the connection’s Manage access tab when they need every name. There is no `shares` key on a row. Every row also carries `access_via` — how the CALLER reaches that connection: "owner", "direct" (shared with them by name), "team" (with `access_via_team`: { id, name } naming the team) or "org" (shared organization-wide). It is about the caller alone, never about anyone else, so it is present on every row including ones where `access_summary` is withheld — and it answers "why can I see this" without disclosing who else can. Credentials are never included. Narrow before paging rather than walking every page: `connector_slug` answers "do we have Slack" exactly (one slug, or several) and is the right choice when the caller names a provider, `owner_user_id` narrows to one owner *within* what the caller can already see (it never reaches a private connection, so it still cannot answer "what has Priya connected"), `status` takes one lifecycle value, and `q` is a case-insensitive substring match against the connection’s name, its account label, its connector slug, and the connector’s catalog label — so `q: "slack"` finds a Slack connection even if a person renamed it to something else, and `q: "sheets"` finds one on `google-sheets` even though the slug does not spell it that way. Unrelated to sso_connection.*, which is how people log IN to Elaichi. Returns { result: [...], nextCursor, prevCursor } — camelCase here, unlike the REST API’s next_cursor. Page by sending nextCursor back as `cursor` until it is null.
    ConnectorOAuth
  • Creates an automation on a perspective. Triggers: per_interview (fires on every completed conversation) or scheduled (daily/weekly, with digest, invite, or insights purpose). Actions: internal insight discovery, webhook, email, or connected provider-backed integrations such as Slack, HubSpot, Gmail, Google Docs, Notion, and Confluence. Execution modes: direct (fast, deterministic, webhook-only) or agent (LLM-powered, required for insights and delivery channels). Behavior: - Each call creates a new automation — even if name/config matches an existing one. - Once enabled, the automation starts firing on real events: per_interview sends on every completed conversation going forward; scheduled sends a real message on the configured cadence (daily/weekly). - For HubSpot, the workspace's HubSpot connection is required — errors with "Could not resolve HubSpot portal ID — please reconnect HubSpot" if not connected. - Webhook channels: do NOT ask the user for the endpoint URL or credentials — neither is accepted through this tool. The automation is created disabled and the response includes configure_url, a web app page where the user sets the URL (and an authentication header if needed). Share that link and ask the user to reply "Done" after saving, then enable the automation via automation_update. - Insight automations use kind "insights", execution_mode "agent", omit channel, and use scheduled purpose "insights" when scheduled. - Errors when the perspective is not found or you do not have access. When to use this tool: - The user wants ongoing notifications on every completed conversation (per_interview). - Building a daily/weekly digest delivered to Slack, email, HubSpot, or a webhook (scheduled). - Running scheduled insight automation which creates insights without external delivery. When NOT to use this tool: - Trying a one-off send before going live — create the automation, then use automation_test (use override_email on email channels to avoid hitting real recipients). - Editing or toggling an existing automation — use automation_update. - Connecting Slack or HubSpot — use integration_manage first; the provider must be connected before slack/hubspot channels work. Example — per-conversation Slack notify (resolve the channel with slack_channel_resolve first, then pass it as resource_id): ``` { "perspective_id": "...", "automation": { "name": "Notify Slack", "trigger": { "type": "per_interview" }, "execution_mode": "agent", "channel": { "type": "composio", "delivery_config": { "provider": "slackbot", "tool_slug": "SLACKBOT_SEND_MESSAGE", "resource_id": "C0123ABCD", "resource_name": "#research" } } } } ``` resource_id is the Slack channel ID or name. The channel is re-verified live on create; an unresolvable channel is rejected. Typical flow: 1. integration_manage (operation: "list"/"connect") → ensure Slack / HubSpot is connected (only needed for those channels) 2. For Slack: slack_channel_search / slack_channel_resolve → find/verify the channel to use as resource_id 3. automation_create → create the automation 4. automation_test (with overrides) → verify delivery before relying on it
    ConnectorOAuth
  • Reset connector auth state for the current user. Use when tokens are stale, missing scopes, tied to the wrong account/workspace, or repeatedly failing auth. For credential-based connectors, this clears the saved credentials so the user can re-enter them. Input: connector_id (required). Supported values: google_workspace, microsoft, dropbox, shopify, shopline, quickbooks, hubspot, slack, ebay, facebook_marketing, tiktok, klaviyo, calendly, activecampaign, odoo, constantcontact, airtable, gohighlevel, monday, semrush, ahrefs, posthog, stripe, gunbroker.
    Connector
    Destructive
    No auth
  • 상담을 이어가고 싶은 사용자의 이메일과 선택 입력한 관심사를 저장합니다. 사용자가 명시적으로 연락받기를 원할 때만 호출하세요. **호출 전 반드시 개인정보 수집 고지를 사용자에게 전달하고 동의를 받으세요** — 개인정보 수집·이용 안내 — 목적: 입시 상담 연락. 수집 항목: 이메일 및 사용자가 직접 입력한 관심사(선택). 보관 기간: 목적 달성 또는 삭제 요청 시까지. 귀하는 동의를 거부할 권리가 있으며, 미동의 시 연락 안내가 제한될 수 있습니다. 삭제 요청·문의: yocan@goanywhere.guru. 자세한 내용: https://goanywhere.guru/privacy 저장 후 온보딩 링크를 안내합니다.
    ConnectorNo auth
  • Turn one piece of raw customer feedback (a Slack message, review, support ticket, or email) into a prioritized, evidence-backed product insight and a PRD problem statement — with the exact verbatim quotes that justify it. No account or API key required. Rate-limited per caller.
    ConnectorNo auth
  • "이 지역 이 물건은 보통 감정가의 몇 %에 낙찰되나"를 실제 매각결과로 답한다. 입찰가를 정할 때 쓰는 핵심 지표다. `by_fail_count`에 유찰 횟수별 분포가 들어 있어 "2회 유찰된 물건은 보통 몇 %에 낙찰되는가"를 바로 읽을 수 있다. 낙찰가율 = 낙찰가 / 감정가 × 100. 100%를 넘으면 감정가보다 비싸게 팔린 것이다. 표본의 집계 기간은 응답의 `sample_period`(매각기일 min~max)에 있다 — "요즘"류 질문에는 이 범위를 함께 전하라. 기간을 좁히는 파라미터는 백엔드가 지원하지 않는다 (요청해도 조용히 무시됨을 실측했다 — 그래서 노출하지 않는다). usage_name에 '빌라'를 넣으면 표준 분류인 '다세대'로 자동 매핑해 집계한다(원문 '빌라'는 소수 비표준 표기 행만 잡혀 표본이 조용히 왜곡된다 — 응답에 매핑 사실이 공시된다). 연립주택 통계는 usage_name='연립주택'으로 따로 물어라. **평형을 섞지 마라(2026-08-16 축 신설)**: 응답의 `by_area_band`가 전용면적대별 낙찰가율이다. 실측(사건 중복 제거): 아파트 전국 전체 79.2%인데 전용 59㎡ 이하 75.7%, 60~84㎡ 82.2%, 서울은 88.9% vs 97.3%다. 대상 물건의 평형을 알면 `area_band`로 좁히고, 지역 요약 하나로 입찰가를 정하지 마라. '면적 미상' 밴드는 공고에 면적 표기가 없는 사건이지 0이 아니다. **이 축의 자리(경매 가격판단 3종 중)**: 이 %는 **감정가 대비** 통계다. 특정 물건이 실거래 **시세** 대비 싼지는 realty_compare_auction_vs_market이 자동 계산한다 — 분모가 다르니 두 %를 한 문장에 섞지 마라(감정가는 시세와 다른 시점·기준의 값이다).
    ConnectorNo auth
  • List the authenticated customer's registered notification channels (Slack or email). Returns JSON. Each entry's `id` is the notification-channel registry UUID — pass this value (not `channelId`) into Fixter alert-rule routing (the `channelIds` parameter of `save_alert_rule` / `set_alert_rule_delivery`, served by a different service). `channelId` is the Slack-side channel id, included for recognition only. `sources` lists the notification sources this channel receives — null means all sources, including future ones.
    ConnectorAPI key
  • MyDART MCP의 find_corp_code 도구는 회사명·종목코드로 DART 법인 식별자(corp_code)의 후보를 확인합니다. [Purpose] - IMPORTANT: first call when a company's corp_code is unknown. - Also to disambiguate same-named companies. - ID resolution only — 업종·data location: get_company_profile; disclosure listings: search_disclosures. [Usage] 1. "카카오" → corp_code 획득 → 재무제표 조회(get_financials) 2. "삼성전자" → corp_code 획득 → 임원 현황 조회(get_periodic_report) 3. "'동양' 들어가는 회사 후보 보여줘" → query="동양", limit=20 4. "005930이 어느 회사야?" → query="005930" [Response] - stock_code: 6-digit present = listed (common shares); empty/absent = unlisted. - count = rows returned (capped by `limit`), not the total match count. 0 hits adds `notes`. [Rules] - `results` is a similarity-ranked candidate array — do not assume the first item is the answer. - corp_code identifies the DART LEGAL ENTITY CODE, not the listing ticker. 우선주/ETF/ETN codes have no mapping (보통주 codes only). - Common names may overflow the default `limit` — raise it when candidates look truncated.
    ConnectorNo auth
  • Use this when the user wants accessibility alerts for a site to go to a Slack channel, or to a different one than now. WRITES to this website's Inclusify configuration, never to the site itself. It CANNOT install Slack: that is a browser OAuth flow on the Inclusify panel's Integrations page and no assistant can do it, so this refuses until the workspace is connected. It also cannot list channels — ask the user for the channel, by name or by Slack channel ID. NOTE THAT THIS POSTS A MESSAGE to the channel before saving, on purpose: a binding that looks right and posts nowhere is worse than a refusal, because the customer believes they are covered. If the post fails — wrong channel, private channel the app was never invited to — nothing is saved and the reason is returned. REQUIRES CONFIRMATION, because it both writes to their Slack and redirects where alerts go. Changing the channel keeps the existing notification settings; only a first-time binding takes the defaults. Use set_slack_events to change which alerts fire. Needs the PRO plan, matching the panel.
    Connector
    Destructive
    API key
  • Decides WHICH kinds of finding get announced, once a channel is already chosen. Reach for it to quieten somewhere noisy, or to switch on something a team keeps missing. WRITES to this website's Inclusify configuration, never to the site itself, and nothing is posted to Slack by this call. Four independent switches plus a threshold, all optional: anything you leave out stays as it is. The site must already have a Slack channel — use set_slack_channel first, and this refuses until then. No confirmation is needed to turn an alert ON. Turning one OFF, or raising the score-drop threshold, means nobody hears about that class of problem any more, so those REQUIRE CONFIRMATION. Needs the PRO plan, matching the panel.
    Connector
    Destructive
    API key
  • List a workspace's Slack channels whose name contains a substring (paged). Reads the indexed channel directory, so it's fast. Read-only — to confirm a specific channel before saving an automation, use slack_channel_resolve. Behavior: - not_connected: Slack isn't connected — connect it via integration_manage (operation "connect") first. - directory_synced: false with an empty result means the directory hasn't been indexed yet — run slack_channel_refresh, then search again. Examples: - `{ "query": "feedback", "limit": 25 }` - `{ }` (list all indexed channels)
    ConnectorOAuth