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

• confirm_publish

  Dreamlit

  Use only after explicit user confirmation and a prior prepare_publish result to publish or schedule a Dreamlit workflow. Side effect: installs live database/repeating/auth triggers, schedules or sends broadcasts, and may enable notification delivery; sandbox mode can hold notifications for inspection. Returns the published workflow status and app URLs. Do not call speculatively or without carrying forward the prepare_publish safety fields.

  Connector

• generate_3d_model

  Sats4AI - Bitcoin-Powered AI Tools

  Convert a single photo into a textured 3D GLB model. Uses Seed3D — generates accurate geometry and materials from one image. Async — returns requestId, poll with check_job_status. 350 sats per model. Pay per request with Bitcoin Lightning — no API key or signup needed. Requires create_payment with toolName='generate_3d_model'.

  Connector

• agent_chat

  Roboflow (Official)

  Chat with the Roboflow AI agent. Use this tool for: - **Roboflow Q&A** — the agent has the full Roboflow documentation indexed (SDKs, REST API, deployment options, training, batch processing, Universe, blocks, pricing, etc.). Ask it anything about how Roboflow works. - **Advanced workflow building** — workflows complex enough that direct block composition via ``workflow_blocks_*`` is impractical. The agent knows every block and connection pattern. - **Solution planning** — pass ``mode="plan"`` and the user's problem; the agent uses a stronger planning model to scope a CV solution end-to-end before any building happens. For straightforward workflows you can construct yourself, the direct ``workflow_*`` tools are fine — you don't have to route every workflow through the agent. ## Conversation flow The agent runs a multi-step conversation. It may ask clarifying questions, recommend a model, or (in plan mode) produce a plan for confirmation. Pass the returned ``conversation_id`` back on follow-up calls to keep context. Use ``agent_conversations_list`` and ``agent_conversation_get`` to find and resume past conversations. ## CRITICAL: the agent NEVER publishes workflows Every workflow the agent creates or edits is saved as a **draft**. The published version that callers using the workflow by id will hit is unchanged until you explicitly publish. To make agent edits live, call ``agent_workflow_publish`` with the workflow ``url`` returned in the chat response. ## Running an agent-built workflow Two options: 1. **Run the draft directly without publishing** — pass the ``specification`` returned in the chat response to ``workflow_specs_run``. Best for testing the draft, or for one-off runs where you don't want to disturb the currently-published version. 2. **Publish, then run by id** — call ``agent_workflow_publish(workflow_url=...)`` then ``workflows_run(workflow_id=..., images=...)``. Use this when you want the change to go live for everyone using the workflow by id. ## Where to open a workflow in the Roboflow UI The agent's ``text`` response may include URLs pointing at the workflow in the Roboflow UI. **Ignore those URLs** — the agent sometimes picks the wrong host or path. Each workflow in the ``workflows`` array has an ``app_url`` field with the correct, environment-aware URL (built from the current ``APP_URL`` plus ``/{workspace}/solutions/chat?workflowUrl=...``) — show that one to the user instead. ## Response shape - ``text`` — the agent's reply. - ``workflows`` — workflows created or edited in this turn, each with ``id``, ``name``, ``url`` (slug), ``app_url`` (clickable Roboflow UI URL — use this), and ``specification`` (the full draft JSON; pass it to ``workflow_specs_run`` to execute without publishing). - ``conversation_id`` — pass back to continue the conversation.

  Connector

• submit_workflow

  Botverse

  Submit a multi-step workflow to the Botverse workflow engine. Steps execute in dependency order; parallel branches (multiple steps with the same depends_on) run simultaneously. Returns a workflow_id immediately — poll get_workflow_status every 5–10 seconds until terminal. Requires auto-refill to be enabled at botverse.cloud/dashboard/billing to prevent mid-workflow balance failures. Workflow definition uses BWDL (Botverse Workflow Definition Language) — schema at botverse.cloud/schemas/workflow/v1.json.

  Connector

• whensport_hr_getVenues

  horse-racing

  Get the horse racing venue list (racecourses). Surface (turf/dirt/all-weather) varies by card and is reported per-meeting, not per-venue.

  Connector

• read_kb_doc

  fixflow

  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.

  Connector

• get_entry_settings

  Sweeppea MCP

  Get entry page settings for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. Returns all configuration: display, colors, spacing, entry settings, compliance, confirmation page, winners page, age gate, AMOE, geolocation, analytics, social media follows, sharing rewards, bonus entries, and sponsor profiles. Use this before update_entry_settings to see current values. # get_entry_settings ## When to use Get entry page settings for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. Returns all configuration: display, colors, spacing, entry settings, compliance, confirmation page, winners page, age gate, AMOE, geolocation, analytics, social media follows, sharing rewards, bonus entries, and sponsor profiles. Use this before update_entry_settings to see current values. ## Pre-calls required 1. fetch_sweepstakes if the user gave you a sweepstakes name instead of a token ## Parameters to validate before calling - sweepstakes_token (string, required) — The sweepstakes token (UUID format)

  Connector

• ceevee_get_report

  CareerProof MCP

  Get report status and metadata (without PDF). Returns status (pending/processing/completed/failed), title, type, inputs, and summary. This is the polling tool for ceevee_generate_report — call every 30 seconds, up to 40 times (20 min max). When status='completed', download PDF with ceevee_download_report(report_id). If status='failed', relay error_message. If still processing after 40 polls, stop and give the user the report_id to check later. Free.

  Connector

• sieve_results

  Sieve

  Get the full results of a completed Sieve analysis. Returns the Sieve Score (0-140), meeting decision (Take Meeting/Pass/ Need More Info), executive summary, key strengths, and key concerns. Args: deal_id: The deal ID returned by sieve_screen. sections: Comma-separated filter (e.g. 'summary,strengths,concerns'). Options: summary, profiles, findings, questions, strengths, concerns. Empty returns everything. Score and decision are always included.

  Connector

• describe_meeting

  Zoning Signal

  Return the full dossier projection for a meeting reading, in the requested cognitive lens. Same lens enum and default as describe_place / describe_corridor — eight total projections (seven stakeholder lenses — developer, investor, broker, attorney, business, resident, civic-leader — plus synthesis as the default). Returns the lens-projected body, full frontmatter (jurisdiction, board, meeting_date, document_type, key_signals, vote tallies), citation-stable claims[] (per the Phase 11 Citable Contract; populates as meeting claim scopes graduate), four-clock freshness, and the structured record_status block (record_type / meeting_status / outcome_status / minutes_available / vote_final) — the last prevents agents from summarizing agenda intent as completed action. Use to ground citations in a specific meeting's reading; pair with list_meetings or meeting_index for discovery.

  Connector

• get_free_resources

  Makuri Showcase (CogniLedger)

  Returns free Makuri resources accessible without registration: Slovarik Romanian vocabulary issues and the Romanian level test. Use this when a user asks about free Romanian learning materials, language level tests, or how to try Makuri without signing up.

  Connector

• get_product_detail

  GuruWalk

  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, itinerary/highlights, images, reviews, pricing, duration, available languages, cancellation policies, guide name (free tours), and meeting point info. Meeting point shape differs by type: paid `product` returns the address text plus coordinates in `where`; `free_tour` returns ONLY a Google Maps URL in `meeting_point_url` (no text address) plus `how_to_find_me` to identify the guide. 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. Always call this tool BEFORE answering questions about a specific tour — never give generic opinions or advice without consulting the real data first.

  Connector

• workflow_specs_run

  Roboflow (Official)

  Execute a Workflow from an inline JSON definition. Unlike ``workflows_run`` which runs a saved workflow by ID, this tool accepts a full workflow JSON spec and executes it directly. Useful for testing workflows before saving them, or for running an agent-built draft without publishing — pass the ``specification`` returned by ``agent_chat``. IMPORTANT: Always call ``workflow_specs_validate`` first to check the definition is valid before running it. IMPORTANT: Images must be public URLs or base64-encoded data. Local file paths do NOT work — the API runs remotely and cannot access your filesystem. Returns workflow outputs as defined by the workflow's output blocks.

  Connector

• vision_query

  DialogBrain

  Look at the screen currently being shared in a meeting and answer a question about it. Returns a natural-language answer based on the visual content. Use ONLY when the user explicitly asks about the screen/slide/document being shown.

  Connector

• workflows_create

  Roboflow (Official)

  Create and save a new Workflow in the workspace. IMPORTANT: Always validate the config with workflow_specs_validate before creating the workflow. The config is the same JSON format used by workflow_specs_run and workflow_specs_validate. Once saved, the workflow can be executed by ID via workflows_run. Returns the created workflow including its document ID. Save this ID — it is required for workflows_update.

  Connector

• agents_add_file

  DialogBrain

  Attach a file to this agent's private knowledge (agent-specific files, not shared with other agents). Workflow: 1. Upload the file with files_upload (pass source_url for remote files) 2. Index it with files_ingest (pass the file_id) 3. Call this tool with agent_id + file_id Returns chunk_count — shows 0 while still processing. Call agents.list_files later to see the final chunk count once indexing completes.

  Connector

• get_workflow_and_preview_url

  Dreamlit

  Read-only. Use before editing, verifying, or preparing publish for an existing workflow. Returns normalized draft and published workflow structure plus the Dreamlit preview/builder URL and status URLs. Do not use to create, update, publish, or unpublish workflows.

  Connector

• workflows_run

  Roboflow (Official)

  Execute a saved Workflow on one or more images. Runs a previously created Workflow against the provided images on the Roboflow serverless infrastructure. This always hits the latest **published** version of the workflow. IMPORTANT: Workflows created or edited via ``agent_chat`` are saved as drafts, not published. If you want to run an agent's latest changes, either call ``agent_workflow_publish`` first, or pass the ``specification`` returned by ``agent_chat`` to ``workflow_specs_run`` to execute the draft directly. IMPORTANT: If processing more than 10 images, spawn a sub-agent to run this tool in the background so the user is not blocked. Returns workflow outputs as defined by the workflow's output blocks.

  Connector

• workflow_blocks_get_schema

  Roboflow (Official)

  Get the full schema of a specific Workflow block. Returns all properties, required fields, and descriptions for a block identified by its manifest name (as returned by ``workflow_blocks_list``).

  Connector

• sign_screenshot_url

  SnapRender

  Generate a signed URL for a screenshot that can be used without an API key. Useful for embedding screenshots in emails, documents, or sharing with third parties. Signing is free, rendering the URL consumes one credit. URLs expire after the specified duration.

  Connector