Skip to main content
Glama
133,431 tools. Last updated 2026-05-13 02:28

"Creating a Gantt Chart from Tasks and Dependencies" matching MCP tools:

  • PREFERRED chart-creation path. Send a structured Builder spec (chart_type + x_col + y_col[s] + optional group_by, palette, axis overrides, annotations) and Autario builds the chart with the same templates the Builder UI uses. Brand attribution (publisher source + autario.com) is applied automatically and cannot be overridden. Insight must cite numbers verifiable against the data | hallucinated numbers return 422 with the available anchor list. For advanced use cases the Builder cannot express, fall back to publish_chart with a freeform plotly_spec. Call chart_instructions() first if unsure of the spec shape.
    Connector
  • Task lists and tasks in workspaces/shares with statuses, priorities, assignees, dependencies, bulk ops. Call action='describe' for the full action/param reference. Destructive: delete-list, delete-task.
    Connector
  • Create multiple tasks in a single operation with escrow calculation. ⚠️ **WARNING**: This tool BYPASSES the standard payment flow by calling db.create_task() directly instead of using the REST API (POST /api/v1/tasks). This means it skips x402 payment verification and balance checks. For production use, tasks should be created via the REST API to ensure proper payment authorization and escrow handling. Supports two operation modes: - ALL_OR_NONE: Atomic creation (all tasks or none) - BEST_EFFORT: Create as many as possible Process: 1. Validates all tasks in batch 2. Calculates total escrow required 3. Creates tasks (atomic or best-effort) - **BYPASSING PAYMENT FLOW** 4. Returns summary with all task IDs Args: params (BatchCreateTasksInput): Validated input parameters containing: - agent_id (str): Your agent identifier - tasks (List[BatchTaskDefinition]): List of tasks (max 50) - payment_token (str): Payment token (default: USDC) - operation_mode (BatchOperationMode): all_or_none or best_effort - escrow_wallet (str): Optional custom escrow wallet Returns: str: Summary of created tasks with IDs and escrow details.
    Connector
  • Get tasks from the Execution Market system with optional filters. Use this to monitor your published tasks or browse available tasks. Args: params (GetTasksInput): Validated input parameters containing: - agent_id (str): Filter by agent ID (your tasks only) - status (TaskStatus): Filter by status (published, accepted, completed, etc.) - category (TaskCategory): Filter by category - limit (int): Max results (1-100, default 20) - offset (int): Pagination offset (default 0) - response_format (ResponseFormat): markdown or json Returns: str: List of tasks in requested format. Examples: - Get my published tasks: agent_id="0x...", status="published" - Get all completed tasks: status="completed" - Browse physical tasks: category="physical_presence"
    Connector
  • Build a complete Tableau dashboard from a CSV file (end-to-end). Pipeline: CSV → schema inference → chart suggestion → Hyper extract → workbook creation → chart configuration → dashboard layout → .twbx output. IMPORTANT FOR AI AGENTS — know before you call: * Auto-selected charts are picked by RULES (data shape + heuristics), NOT by natural-language chart requests. To guarantee a specific chart (e.g. "top 10 customers by profit") you MUST pass it via ``required_charts``; otherwise it may or may not be generated and may be trimmed out by ``max_charts``. * The user's reference image is NOT automatically read from the chat. If the user asks for styling "like this image", you must save the image to disk and pass its path via ``reference_image``. * This tool returns a STRUCTURED MANIFEST dict describing what was actually built. Always cite fields from the returned manifest (worksheets / theme / dashboards) when describing the result to the user — do NOT invent charts that are not listed there. Args: csv_path: Path to the source CSV file. output_path: Output .twbx path (defaults to <csv_stem>_dashboard.twbx). dashboard_title: Dashboard title (derived from filename if empty). max_charts: Maximum number of charts (0 = use dashboard_rules.yaml default). template_path: TWB template path (empty for default template). theme: Theme preset name (empty = use dashboard_rules.yaml default). Options: modern-light, modern-dark, classic, minimal, vibrant. rules_yaml: Optional YAML string with dashboard rules overrides. Example: "kpi:\n font_size: 32\n max_kpis: 3" required_charts: Optional list of chart specs that MUST be built. Each entry is a dict, for example:: {"title": "Top 10 Customers by Profit", "kind": "bar", "rows": "Customer Name", "columns": "SUM(Profit)", "top_n": 10, "top_by": "SUM(Profit)", "sort_descending": "SUM(Profit)"} Supported kinds: bar, line, scatter, pie, map, heatmap, tree_map, text. Required charts bypass dedup + trim. reference_image: Optional path to a PNG/JPG whose palette should drive the dashboard styling. Applied AFTER the theme so image colours win. The path must exist on disk; chat attachments need to be saved first. Returns: Structured manifest dict with keys: ``status``, ``output_path``, ``source``, ``dashboards``, ``worksheets``, ``charts_built``, ``required_charts_fulfilled``, ``dropped_suggestions``, ``theme``, ``warnings``, ``summary``. Cite THIS dict when describing results.
    Connector
  • Score all gallery templates and recommend the best fit. Call this AFTER profiling the data source and deciding on chart types, but BEFORE creating the dashboard layout. The decider evaluates every template in the gallery against the data profile and chart mix, returning a ranked list with reasoning. Args: chart_types: Comma-separated list of chart mark_types being built. Example: "Bar,Line,Text,Text,Map" If omitted, uses only the data profile signals. kpi_count: Override KPI count (else derived from chart_types). Returns: Ranked template recommendations with scores and reasoning.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Create multiple tasks in a single operation with escrow calculation. ⚠️ **WARNING**: This tool BYPASSES the standard payment flow by calling db.create_task() directly instead of using the REST API (POST /api/v1/tasks). This means it skips x402 payment verification and balance checks. For production use, tasks should be created via the REST API to ensure proper payment authorization and escrow handling. Supports two operation modes: - ALL_OR_NONE: Atomic creation (all tasks or none) - BEST_EFFORT: Create as many as possible Process: 1. Validates all tasks in batch 2. Calculates total escrow required 3. Creates tasks (atomic or best-effort) - **BYPASSING PAYMENT FLOW** 4. Returns summary with all task IDs Args: params (BatchCreateTasksInput): Validated input parameters containing: - agent_id (str): Your agent identifier - tasks (List[BatchTaskDefinition]): List of tasks (max 50) - payment_token (str): Payment token (default: USDC) - operation_mode (BatchOperationMode): all_or_none or best_effort - escrow_wallet (str): Optional custom escrow wallet Returns: str: Summary of created tasks with IDs and escrow details.
    Connector
  • Get pre-built graph template schemas for common use cases. ⭐ USE THIS FIRST when creating a new graph project! Templates show the CORRECT graph schema format with: proper node definitions (description, flat_labels, schema with flat field definitions), relationship configurations (from, to, cardinality, data_schema), and hierarchical entity nesting. Available templates: Social Network (users, posts, follows), Knowledge Graph (topics, articles, authors), Product Catalog (products, categories, suppliers). You can use these templates directly with create_graph_project or modify them for your needs. TIP: Study these templates to understand the correct graph schema format before creating custom schemas.
    Connector
  • Return step-by-step instructions for creating a Kamy API key in the dashboard. Does not open the browser.
    Connector
  • Use when you need the full natal chart for interpretation, comparison, or downstream transit/progression work. Returns planets, houses, aspects, patterns, dignities, and Big Three. `detail="compact"` drops the per-aspect details (keeps `aspects.summary` counts) and per-pattern planet lists — saves ~15k tokens on a typical chart, useful when you only need placements + angles. Next step: if you need aspect-by-aspect narrative material, call with `detail="full"`; for transits to this chart, call `current_transits` or `transit_search` with the same birth data.
    Connector
  • Patch a single chart in an existing dashboard by chart ID. Provide only the chart fields to change. Set a field to null to remove it. Use overwrite=true to skip version conflict checks, or provide the current dashboard version for optimistic concurrency control.
    Connector
  • Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.
    Connector
  • Audit the supply chain risk of a GitHub repository's dependencies. Fetches the repo's package.json and/or requirements.txt from GitHub and runs behavioral commitment scoring on every dependency. This is the fastest way to audit a project — just provide the GitHub URL or owner/repo slug, and get a full risk table in seconds. Risk flags: - CRITICAL: single publisher/maintainer/owner + >10M weekly downloads (publish-access concentration risk) - HIGH: sole publisher/maintainer + >1M/wk downloads, OR new package (<1yr) with high adoption - WARN: no release in 12+ months (potential abandonware) Examples: - "vercel/next.js" — audit Next.js dependencies - "https://github.com/langchain-ai/langchainjs" — audit LangChain JS - "facebook/react" — audit React's dependency tree - "anthropics/anthropic-sdk-python" — audit Anthropic Python SDK Use this when someone asks "is my project at risk?" or "audit this repo's dependencies".
    Connector
  • Map the full dependency tree of an npm package and identify CRITICAL supply chain risks at every level. Unlike auditing a flat list of packages, this tool traverses the dependency graph — showing not just your direct dependencies but also what your dependencies depend on. Hidden CRITICAL packages (sole publisher + >10M weekly downloads) often lurk 1-2 levels deep. Risk flags: - CRITICAL: single npm publisher + >10M weekly downloads — sole point of failure for a massive attack surface - HIGH: sole publisher + >1M/wk, OR new package (<1yr) with high adoption - WARN: no release in 12+ months (potential abandonware) depth=1 (default): root package + all direct dependencies depth=2: also traverses one more level for any CRITICAL/HIGH direct deps (reveals hidden exposure) Examples: - audit_dependency_tree("express") — see all of Express's deps and their risk scores - audit_dependency_tree("langchain", 2) — reveal transitive CRITICAL deps 2 levels deep - audit_dependency_tree("@anthropic-ai/sdk") — audit Anthropic SDK full tree Use this when someone asks: - "What am I really depending on?" - "Are my dependencies' dependencies safe?" - "Show me the full supply chain risk for package X"
    Connector
  • Search recipes by keyword across titles, descriptions, tags, and full source code. Use for any iOS, SwiftUI, or backend topic — e.g. subscription, authentication, camera, animation, chart, onboarding, paywall, infrastructure.
    Connector
  • Search tasks with optional filters. Returns both real tasks and projected recurring task instances. When a date range is provided (scheduled_date, scheduled_date_from/to), virtual recurring instances are automatically included. Virtual tasks have is_virtual=true and IDs starting with "virtual:". They can be passed directly to update_task or delete_task. Filter conflicts: scheduled_date and scheduled_date_from/to are mutually exclusive. unscheduled=true cannot be combined with date filters. Use to find tasks by keyword, date, priority, tags, or completion status. Use without filters to get recent tasks.
    Connector
  • Publish a task to make it visible to operators. Works for both settlementMode='escrow' and 'direct' tasks. The task must be in Draft or Funded status. For escrow Draft tasks: funds are automatically reserved and locked from your wallet (requires sufficient balance). For direct-settlement Draft tasks: no funding happens — the task goes directly from Draft to Published because the client pays the operator on-site (no escrow). This is the intended shortcut for direct-settlement. For Funded tasks (after escrow Quote → Fund flow): the funds are already locked, the task is simply made visible. After publishing, operators can accept the task. Requires authentication. Next: wait for task.accepted via get_task_events or webhook.
    Connector
  • Generate a Markdown overview of all tasks grouped by status (in_progress, blocked, open, null, done) with completion percentages. Tasks without history appear under "Geen status". Includes recent activity from today and yesterday. Use this at the start of a session for a quick backlog overview, or to share current status.
    Connector