Skip to main content
Glama
619,142 tools. Updated 2026-09-28 13:21

"A workflow for processing and sharing meeting-related materials" matching MCP tools:

  • Start a run of a deployed multi-step workflow on a document (workflows group; not runnable until a version is deployed, or pass version "draft"). Workflow runs commonly take minutes to hours. Async: a status: "running" result with a runId is not an error — resume with get_workflow_run passing that runId, the same workspaceId and environment, and wait: true, repeating until the status is terminal; never re-submit the document. On UNAUTHORIZED or NOT_FOUND, re-call get_me for the granted targets. Statuses: PROCESSED; FAILED (retryable: true means the failureReason is usually transient and one retry is reasonable); NEEDS_REVIEW (paused for a human reviewer in the dashboard — share dashboardUrl with the user and re-check the run after they finish; do not retry or re-submit); REJECTED (a reviewer rejected the run in the dashboard — final; dashboardUrl has their reasoning); CANCELLED. For one merged run over 2-50 related files, pass package instead of file. outputs injects pre-computed results for specific extractors/classifiers/splitters so the workflow skips recomputing them (not allowed with package).
    ConnectorOAuth
  • Finish an upload started with create_upload and begin processing. Pass the `video` id (hashid) returned by create_upload, AFTER you have PUT the file bytes to its upload_url. Queues the video for processing and returns its `id` and current `status`. The outcome (`processing`, or `pending_credits` if the team is out of credits) is settled a moment later, so poll get_video_status for it. If the file hasn't been uploaded yet, an error is returned: upload it, then retry.
    ConnectorOAuth
  • Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card trial. For a scored workflow diagnosis, use audit_lead_workflow; for replay testing, use get_leadproof_replay_trial; for paid checkout, use get_leadproof_checkout only after authorization.
    ConnectorNo auth
  • Read a revision's scene from its stored structured summary — synchronous, no container. detail: summary | objects | materials | render | cameras | lights | stats | full. Use "cameras" to get camera ids for render_create cameraId, "lights" for the rig with energies, and "stats" for per-object vertex/face counts, UV presence and modifier stacks. Filter with objectIds, or with namePattern/excludeNamePattern — namePattern is how you turn the `namePattern` a copying operation reports (object.radial_array, object.array_along_curve) back into the full list of ids it created. limit/cursor page the requested entity type. In full mode each included collection uses the same offset/limit; nextCursor continues while any collection has more rows. Object filters affect objects, cameras and lights; materialIds independently filters materials. For exact node names, links and packed image bindings request includeNodeGraphs with detail=materials/full and one materialId or limit=1. Graphs are omitted by default; legacy or partial summaries explicitly report availability. All positions and sizes are metres (1 unit = 1000 mm).
    ConnectorOAuth
  • Get the full detail of one or more tours or activities on GuruWalk in a single call. Pass an `items` array — each entry has its own type, product_id and language, and is processed independently. Returns a `results` array where every entry echoes its `product_id` and `type` so you can match each response to its request. Always batch when you need details for several tours (e.g. before recommending or comparing them): send them all in one call instead of invoking this tool several times. Each successful entry returns description, images, reviews, duration, available languages, cancellation policies, and meeting point info. Paid `product` entries also return `highlights`, `included`/`excluded`, `pricing_from`, and `where` (address + coordinates). `free_tour` entries return `itinerary` as a flat array of point-title strings (no descriptions), plus `guide.name`, `meeting_point_url`, and `how_to_find_me`. Both types return `meeting_point_url` (Google Maps link) whenever the meeting point has coordinates. For a `free_tour` that is the meeting point. For a paid `product` it is the reference point published on the listing: useful to orient a traveler who has not booked yet, but the operative meeting point of a purchased activity — with the supplier's own instructions — is the one in its voucher. Offer it as a reference, never as the confirmed meeting point of a booking. Paid `product` also returns the address text and coordinates in `where`; `free_tour` also returns `meeting_point_latitude` and `meeting_point_longitude` (use these coords as destination for routing), plus `how_to_find_me`: a free-text note written by the guide describing how the traveler can recognize them at the meeting point. Per-item errors (product not found) are reported inside that item's result without failing the rest of the batch. Use this tool whenever the traveler asks what a tour covers, which places it visits, its itinerary, route, description, meeting point, duration, or any content-related question. For the meeting point of a paid activity the traveler has already booked, the booking's voucher comes first; fall back to this tool only when that voucher has no meeting point yet, and say then that this is the point published on the listing and that the definitive one arrives with the voucher. Always call this tool BEFORE answering questions about a specific tour — never give generic opinions or advice without consulting the real data first. Supports en, es, de, it; any other value falls back to English. Pass the traveler's language code anyway and translate the answer into their language. Each result includes the tour's url — when recommending or confirming a tour, share it so the traveler can open it to book.
    ConnectorNo auth
  • Workflow versioning — add a new version to an EXISTING workflow (by workflow_id) to evolve a workflow you already created. Author the new version's definition against the schema from get_workflow_definition_schema. Like create_workflow, the definition is statically validated BEFORE it is written: error-severity findings mint nothing (valid=false, created=false), and a successful write returns any advisory (warning/info) findings. Pass publish=true to publish this workflow version immediately, or later with publish_workflow. (For a brand-new workflow, use create_workflow.)
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides computed (DFT) materials structures and thermodynamic properties through the Pipeworx MCP gateway, enabling AI agents to query materials data via natural language or tool calls.
    4 npm
    MIT

Matching MCP Connectors

  • Materials MCP — computed (DFT) materials structures & thermodynamic properties.

  • Build and manage Cloudgate workflow-APIs: controllers, actions, workflow graphs, and databases.

  • Discover subsidiary and related company names using FDA datasets first, then supplement with external corporate hierarchy sources (SEC EDGAR Exhibit 21 and GLEIF) when available. Costs 2 credits. Returns FDA name candidates, evidence-backed company-record suggestions, EDGAR subsidiaries, GLEIF subsidiaries, existing aliases, and facility coverage stats. The coverage.unlinked_feis count indicates how many facilities may be missing from the current alias set. The workflow is conservative and explainable: it validates candidates against FDA company records instead of auto-linking them. Note: EDGAR and GLEIF may lag recent acquisitions or divestitures, so missing external results do not rule out FDA-visible subsidiaries. Recommended workflow: 1. fda_suggest_subsidiaries, 2. fda_link_subsidiaries for distinct child companies or fda_save_aliases for true same-company variants, 3. fda_manufacturing_risk_summary or fda_search_family_facilities. Related: fda_link_subsidiaries (persist explicit family links), fda_save_aliases (persist same-entity names), fda_manufacturing_risk_summary (family-aware company rollup), fda_search_family_facilities (family-aware FEI search).
    ConnectorNo auth
  • Deducts a unit from the customer's available workflow allowance. Do not call this tool when the customer is requesting assistance related to the pay wall and its subscriptions. This tool should be called after each AI response that is not pay wall related. @param customer_id: The customer's database id @return: a json object, containing the customer_id and remaining fup token balance in the "values" object
    ConnectorNo auth
  • Use after explicit user intent to unpublish a Dreamlit workflow. Side effect: disables live triggers or schedules for that workflow and stops future automated sends. Returns updated workflow status and app URLs. Do not use for deleting drafts, canceling one broadcast run, or editing workflow content.
    Connector
    Destructive
    No auth
  • Lists Zoom meeting recordings saved locally on this Mac (~/Documents/Zoom), newest first: meeting name, date, and which artifacts exist (transcript, captions, saved chat, audio, video). Local recordings only — no Zoom API, no admin approval. Use zoom_read_transcript to read the text of a meeting.
    ConnectorOAuth
  • Sell a towed wreck to an NPC salvage yard for credits (Must be docked at an NPC station with a salvage yard. The yard keeps the hull's materials and cargo and pays a fraction of their local market value from the station manager's credits; a broke manager can't buy. Player-owned yards don't buy wrecks. Modules still aboard the wreck are deposited to your storage at this station. scrap_wreck recovers far more, as materials.)
    ConnectorNo auth
  • Use this when the user attaches an audio recording — a meeting, call, interview, lecture or voice note — and wants it transcribed or turned into meeting notes or minutes of meeting (MoM). MeetNotes returns a speaker-labelled transcript plus minutes: summary, key points, decisions and action items with owners. Handles over 100 languages and mixed-language speech such as Hindi with English (Hinglish). For meetings already in MeetNotes use search or meetnotes_list_recordings instead. Returns a job receipt at once; processing continues on the server and spends the connected account's minutes. Poll meetnotes_get_job with job_id, then read the meeting with fetch or meetnotes_get_transcript. The same file twice returns the same meeting with deduplicated true and is never processed or charged again. Audio files only, within the size limit from meetnotes_get_capabilities.
    Connector
    Destructive
    OAuth
  • SECOND STEP in the troubleshooting workflow. Read the full content and solution of a specific Knowledge Base card. Returns the card content WITH reliability metrics and related cards so you can assess trustworthiness and explore connected issues. WHEN TO USE: - Call this ONLY after obtaining a valid `kb_id` from the `resolve_kb_id` tool. INPUT: - `kb_id`: The exact ID of the card (e.g., 'CROSS_DOCKER_001'). OUTPUT: - Returns reliability metrics followed by the full Markdown content of the card, plus related cards. - You MUST apply the solution provided in the card to resolve the user's issue. - After applying, you MUST call `save_kb_card` with `outcome` parameter to close the feedback loop.
    ConnectorNo auth
  • Pause, resume, delete, or instantiate a workflow. Workflow authoring lives in the visual editor — this tool only handles lifecycle actions and template cloning. To build a workflow from scratch, point the user at the editor. Actions: - 'pause' / 'resume' / 'delete': Require `workflow_id`. - 'from_template': Create a new workflow from a template id. Optional `name` overrides the template's default title. Use get_workflows(view='templates') to find the template_id. Args: brand_id: The brand the workflow belongs to (required). action: Lifecycle action. workflow_id: Required for pause/resume/delete. template_id: Required for 'from_template'. name: Optional name override for 'from_template'.
    Connector
    Destructive
    OAuth
  • Remove a document from a workflow/envelope. Soft-deletes the file via DELETE /api/v3/files/:fileId, resets related signing history, and optionally removes the Monday file-column asset when asset_id is provided. Confirm with the user before calling — this mutates the envelope. Use getsign_list_envelope_documents first to discover file_id / asset_id.
    Connector
    Destructive
    OAuth
  • Status of a job: an export job id from meetnotes_export_meeting, a notetaker job id from meetnotes_invite_notetaker, or a meeting/recording id while it is processing. Poll no sooner than next_poll_after_seconds. A completed meeting job includes minutes_markdown — the full minutes — to show the user.
    ConnectorOAuth
  • Single-product classification. Accepts a free-text description plus optional structured hints (materials, intended_use, category, origin/destination country). POPULATE EVERY HINT YOU HAVE — materials/intended_use/category materially improve retrieval and candidate quality vs a description-only call (e.g. description:"Funko POP Vinyl", category:"Figurines", materials:["PVC plastic"], intended_use:"decorative collectible figure" reliably surfaces ch. 95). Returns top-3 CN candidates, EUDR scope, MFN duty, a bilingual reasoning_md narrative, a gap_analysis flagging missing inputs, and a tri-state status (confident / review_recommended / manual_review_required). Trust `status` for review-routing — do not re-derive your own confidence threshold. PAT-authed callers also receive prior_decisions[] from the org dictionary history.
    ConnectorNo auth
  • Fetch the full machine-readable rendition of a tutorial by slug: title, TL;DR, numbered steps (with text, imageUrl, tips, and YouTube videoTimestampSeconds for deep-linking), tools/materials, tags, related tutorial slugs, creator credit, recipe (with nutrition + cuisine when applicable), license, and canonicalUrl. Use this after search_tutorials to fetch step details.
    ConnectorNo auth
  • Start a NEW Echosaw analysis job from a publicly accessible media or document URL, or a video platform URL (YouTube, Rumble, Vimeo, etc.). Accepts video, audio, image, and document (PDF, TXT, MD, PPTX) inputs. This is an entry point that creates a job and begins processing — it does not fetch previously analyzed media (use echosaw_download_media for that). Returns a job ID (mediaId) used to track processing and retrieve results.
    ConnectorOAuth
  • Whole-life embodied carbon for materials, per EN 15978. Give a material key + quantity (+ optional boundary A1-A3 / A1-A4 / A1-A5 / A1-C); it assembles the declared lifecycle modules (A1-A3, B, C1-C4, D) into stages, totals the boundary, reports module D separately, and flags any missing stage as not-assessed (never zero). Find material keys via search_factors (section "materials").
    ConnectorNo auth