Skip to main content
Glama
114,463 tools. Last updated 2026-04-21 13:18
  • Get Arcadia workflow guides and reference documentation. Call this before multi-step workflows (opening LP positions, enabling automation, closing positions) or when you need contract addresses, asset manager addresses, or strategy parameters. Topics: overview (addresses + tool catalog), automation (rebalancer/compounder setup), strategies (step-by-step templates), selection (how to evaluate and parameterize strategies).
    Connector
  • Score up to 25 workflow items sequentially in one request for healthcare workflow automation.
    Connector
  • ⚠️ MANDATORY FIRST STEP - Call this tool BEFORE using any other Canvs tools! Returns comprehensive instructions for creating whiteboards: tool selection strategy, iterative workflow, and examples. Following these instructions ensures correct diagrams.
    Connector
  • WHEN: user explicitly asks to post, add, or save a comment to an ADO Work Item. [~] PRIORITY TRIGGER: call AFTER `ado_analyze_workitem` when user says 'post the analysis', 'save it to the ticket', 'ajoute en commentaire'. WARNING: ALWAYS ask for explicit user confirmation before calling this tool. Recommended workflow: (1) call `ado_analyze_workitem`, (2) show analysis to the user, (3) ask 'Shall I post this comment to Work Item #X?', (4) only then call this tool. Requires DEVOPS_ORG_URL + DEVOPS_PAT with Work Items: Write permission.
    Connector
  • Execute a saved Workflow on one or more images. Runs a previously created Workflow against the provided images on the Roboflow serverless infrastructure. 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

Matching MCP Servers

Matching MCP Connectors

  • AI-native team workspace — tables, documents, workflow automation, live dashboards & analytics

  • AI-powered intelligence for your development workflow via Indicate.

  • Update an existing saved Workflow's name and definition. IMPORTANT: Always validate the config with workflow_specs_validate before updating the workflow. Use workflows_get to retrieve the current workflow first, then modify the config as needed.
    Connector
  • 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
  • Execute a Workflow from an inline JSON definition. Unlike ``run_workflow`` which runs a previously saved workflow by ID, this tool accepts a full workflow JSON spec and executes it directly. This is useful for testing workflows before saving them. IMPORTANT: Always call ``workflow_specs_validate`` first to check the definition is valid before running it. 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
  • List all available Workflow blocks with a short summary of each. Use this tool to discover which blocks can be used when building a Workflow definition. To get the full schema (properties, required fields, etc.) of a specific block, call ``workflow_blocks_get_schema`` with the block's ``manifest`` name. Returns a list of blocks, each with manifest (schema key), name, block_type, and short_description.
    Connector
  • Validate a Workflow JSON definition without executing it. Use this tool to check whether a workflow definition is syntactically and semantically correct before saving or running it. The definition should follow the standard Workflow format with version, inputs, steps, and outputs. IMPORTANT: Always validate a workflow definition before running it. Example workflow definition — detects objects, enlarges bounding boxes, crops, runs a second detection filtering for dogs, and classifies the breed only when exactly one dog is found: .. code-block:: json { "version": "1.0", "inputs": [ {"type": "WorkflowImage", "name": "image"} ], "steps": [ { "type": "ObjectDetectionModel", "name": "first_detection", "image": "$inputs.image", "model_id": "yolov8n-640" }, { "type": "DetectionsTransformation", "name": "enlarging_boxes", "predictions": "$steps.first_detection.predictions", "operations": [ {"type": "DetectionsOffset", "offset_x": 50, "offset_y": 50} ] }, { "type": "Crop", "name": "first_crop", "image": "$inputs.image", "predictions": "$steps.enlarging_boxes.predictions" }, { "type": "ObjectDetectionModel", "name": "second_detection", "image": "$steps.first_crop.crops", "model_id": "yolov8n-640", "class_filter": ["dog"] }, { "type": "ContinueIf", "name": "continue_if", "condition_statement": { "type": "StatementGroup", "statements": [ { "type": "BinaryStatement", "left_operand": { "type": "DynamicOperand", "operand_name": "prediction", "operations": [{"type": "SequenceLength"}] }, "comparator": {"type": "(Number) =="}, "right_operand": { "type": "StaticOperand", "value": 1 } } ] }, "evaluation_parameters": { "prediction": "$steps.second_detection.predictions" }, "next_steps": ["$steps.classification"] }, { "type": "ClassificationModel", "name": "classification", "image": "$steps.first_crop.crops", "model_id": "dog-breed-xpaq6/1" } ], "outputs": [ { "type": "JsonField", "name": "dog_classification", "selector": "$steps.classification.predictions" } ] } Key patterns shown above: - ``$inputs.<name>`` references a workflow input. - ``$steps.<step_name>.<output>`` references another step's output. - ``ContinueIf`` enables conditional branching based on runtime values. - Steps can chain: detect → transform → crop → detect → classify. Returns validation status. A valid workflow returns ``{"status": "ok"}``. An invalid one returns error details.
    Connector
  • Encode args for the standalone yield claimer automation. Periodically claims pending fees/emissions and sends them to a designated recipient (wallet, another account, or any address). Returns { asset_managers, statuses, datas } — pass to write_account_set_asset_managers. Combinable with other intent tools.
    Connector
  • Save normalized alias names for a parent company, updating confidence and tracking collisions. Use this for true name variants of the same company record. If a collision says the alias already belongs to another company_id, use fda_link_subsidiaries instead of forcing the alias. Typical workflow: call fda_suggest_subsidiaries first, review results, then call this tool with confirmed same-entity alias names.
    Connector
  • List all available automation intents with their tool names, required parameters, and supported chains. Use this to discover which automations can be configured and what each one does. Each intent has a corresponding write_asset_manager.{id} tool that returns encoded args. To apply automations, call the intent tools then pass the combined result to write_account_set_asset_managers. All intent tools accept enabled=false to disable. Multiple intents can be combined by merging their returned arrays into a single set_asset_managers call.
    Connector
  • Execute a tool by name with the provided arguments. IMPORTANT: You MUST call TOOL_GET(tool_name) first to retrieve the full parameter schema before calling this tool. The arguments must match the schema returned by TOOL_GET, including all required parameters. Calling without the correct arguments will result in errors. Workflow: TOOL_LIST -> TOOL_GET(tool_name) -> TOOL_CALL(tool_name, arguments)
    Connector
  • Load fundamental analysis workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks about company valuation, financial health, investment quality, earnings trends, profitability, "is X a good buy", or any deep-dive company analysis. Can be combined with other workflow tools.
    Connector
  • Load fundamental analysis workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks about company valuation, financial health, investment quality, earnings trends, profitability, "is X a good buy", or any deep-dive company analysis. Can be combined with other workflow tools.
    Connector
  • Load technical analysis workflow with indicator interpretation guide and advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks about RSI, MACD, moving averages, support/resistance, overbought/oversold, chart patterns, momentum, trend analysis, or entry/exit signals. Can be combined with other workflow tools.
    Connector
  • Load comparative analysis workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks to compare companies, "X vs Y", peer benchmarking, sector ranking, or relative valuation. Can be combined with other workflow tools.
    Connector
  • Load quantitative screening workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks to find, screen, rank, or filter stocks by multiple criteria — "find stocks that...", "top N by...", sector-wide ranking, or any multi-factor selection. Can be combined with other workflow tools.
    Connector
  • WHEN: user asks how an approval workflow works, who approves a document, what states it goes through, or what happens on submission/rejection. NOT for technical workflow class details -- use `get_object_details`. WORKFLOW EXPLAINER (Business Language) -- Explains a D365 approval workflow: who approves, what states exist, and what happens on approval or rejection. Output is plain business language -- no X++ or workflow engine jargon. Triggers: 'explain the workflow for', 'how does the approval work', 'qui approuve', 'workflow states for', 'étapes du workflow', 'approval process for', 'circuit d\'approbation', 'what happens when a user submits'.
    Connector
  • Retrieves information to determine whether a broker is legitimate or a scam. This tool can look up brokers using either their company name or website URL. It returns verification data, scam reports, regulatory status, and trustworthiness indicators to help assess the broker's credibility. Use this tool when users ask about broker reliability, safety, legitimacy, or want to verify if a specific broker is trustworthy before investing or trading.
    Connector
  • Scaffold a new Klever smart contract project using the SDK. Creates the Rust project structure via `ksc new` and generates automation scripts (build, deploy, upgrade, query, test, interact). Requires Klever SDK installed at ~/klever-sdk/. Run check_sdk_status first to verify. NOTE: In public profile, this tool returns a project template JSON and does not perform any filesystem changes.
    Connector
  • Load earnings analysis workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks about earnings results, EPS surprises, beat/miss history, earnings estimates, quarterly reporting, or earnings season analysis. Can be combined with other workflow tools.
    Connector
  • Load quantitative screening workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks to find, screen, rank, or filter stocks by multiple criteria — "find stocks that...", "top N by...", sector-wide ranking, or any multi-factor selection. Can be combined with other workflow tools.
    Connector
  • Load comparative analysis workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks to compare companies, "X vs Y", peer benchmarking, sector ranking, or relative valuation. Can be combined with other workflow tools.
    Connector
  • Add build, deploy, upgrade, query, test, and interact automation scripts to an existing Klever smart contract project. Creates a scripts/ directory with bash scripts and updates .gitignore. Run this from the project root directory (where Cargo.toml is located). NOTE: In public profile, this tool returns a project template JSON and does not perform any filesystem changes.
    Connector
  • WHEN: user explicitly asks to post, add, or save a review comment to an ADO Pull Request. [~] PRIORITY TRIGGER: call AFTER `ado_analyze_pr_impact` when user says 'post the review', 'add comment to PR', 'ajoute le commentaire sur la PR'. WARNING: ALWAYS ask for explicit user confirmation before calling this tool. Recommended workflow: (1) call `ado_analyze_pr_impact`, (2) show the result, (3) ask 'Shall I post this review comment to PR #X?', (4) only then call this tool. Requires DEVOPS_ORG_URL + DEVOPS_PAT (Pull Request Threads: Read & Write).
    Connector
  • Load earnings analysis workflow with advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks about earnings results, EPS surprises, beat/miss history, earnings estimates, quarterly reporting, or earnings season analysis. Can be combined with other workflow tools.
    Connector
  • Load technical analysis workflow with indicator interpretation guide and advanced query patterns. REQUIRES get_database_schema to be called first — this tool has no schema. Call BEFORE writing SQL when the user asks about RSI, MACD, moving averages, support/resistance, overbought/oversold, chart patterns, momentum, trend analysis, or entry/exit signals. Can be combined with other workflow tools.
    Connector
  • Create an inbound or outbound webhook for an agent. Inbound: receive messages via HTTP POST. Outbound: send events to your URL (n8n, Zapier, Make compatible).
    Connector
  • Retrieve detailed information about a specific company in Teamwork Desk by its ID. Useful for auditing company records, troubleshooting ticket associations, or integrating Desk company data into automation workflows.
    Connector
  • Retrieve detailed information about a specific ticket type in Teamwork Desk by its ID. Useful for auditing type usage, troubleshooting ticket categorization, or integrating Desk type data into automation workflows.
    Connector
  • Retrieve detailed information about a specific customer in Teamwork Desk by their ID. Useful for auditing customer records, troubleshooting ticket associations, or integrating Desk customer data into automation workflows.
    Connector
  • Retrieve detailed information about a specific user in Teamwork Desk by their ID. Useful for auditing user records, troubleshooting ticket assignments, or integrating Desk user data into automation workflows.
    Connector
  • Retrieve detailed information about a specific ticket in Teamwork Desk by its ID. Useful for auditing ticket records, troubleshooting support workflows, or integrating Desk ticket data into automation and reporting systems.
    Connector
  • Retrieve detailed information about a specific status in Teamwork Desk by its ID. Useful for auditing status usage, troubleshooting ticket workflows, or integrating Desk status data into automation workflows.
    Connector
  • Get an existing stage within a workflow in Teamwork.com. A workflow stage is a single step within a workflow in Teamwork.com. Stages are ordered and define the progression path for tasks as they move through the workflow from start to completion. Each stage belongs to a parent workflow.
    Connector
  • List stages within a workflow in Teamwork.com. A workflow stage is a single step within a workflow in Teamwork.com. Stages are ordered and define the progression path for tasks as they move through the workflow from start to completion. Each stage belongs to a parent workflow.
    Connector
  • Trigger content generation for an automation immediately. Creates posts based on the automation config.
    Connector
  • Retrieve detailed information about a specific tag in Teamwork Desk by its ID. Useful for auditing tag usage, troubleshooting ticket categorization, or integrating Desk tag data into automation workflows.
    Connector
  • Retrieve detailed information about a specific priority in Teamwork Desk by its ID. Useful for inspecting priority attributes, troubleshooting ticket routing, or integrating Desk priority data into automation workflows.
    Connector
  • Create a new bulk job for sending messages to multiple recipients. Workflow: create_bulk_job → add_bulk_users → run_bulk_job.
    Connector
  • Run a supported Monte Carlo workflow and return either the structured report payload or a PDF or DOCX artifact.
    Connector
  • Update an existing ticket in Teamwork Desk by ID, allowing changes to its attributes. Supports evolving support processes, correcting ticket records, or integrating with automation systems for improved ticket handling.
    Connector